You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for making your work available to all of us!
I'm currently working on adding type hints to a project that uses the noise package. Since most of the functions & methods in this package - especially the ones defined in extension modules - do not make use of Python's dynamic typing, it seems possible and useful to add type hints here, aswell.
PEP 561 defines how to distribute type information with a python package, the documentation for mypy gives a good summary:
Type hints can either be distributed inline with the python code, or
Type stub files can be distributed within the same package, or
a separate stub files package called <packagename>-stubs can be created
I'd be willing to do all the work.
If you are in favor of adding type hints to the noise package, which way would you prefer, inline or as stub files? If you're opposed to adding type hints, would you mind if I create a noise-stubs package and publish it to PyPI?
The text was updated successfully, but these errors were encountered:
First of all, thanks for making your work available to all of us!
I'm currently working on adding type hints to a project that uses the
noise
package. Since most of the functions & methods in this package - especially the ones defined in extension modules - do not make use of Python's dynamic typing, it seems possible and useful to add type hints here, aswell.PEP 561 defines how to distribute type information with a python package, the documentation for mypy gives a good summary:
<packagename>-stubs
can be createdI'd be willing to do all the work.
If you are in favor of adding type hints to the
noise
package, which way would you prefer, inline or as stub files? If you're opposed to adding type hints, would you mind if I create anoise-stubs
package and publish it to PyPI?The text was updated successfully, but these errors were encountered: