ffaa0ea3d1
* Added initial rework of the concurrent.futures module * Minor fixes * Fixed some generics & changed to collections over typing for some types * Switched thread to use queues instead of multiprocessing.queues * More fixes * More fixes following results from running tests locally * Tmp commit of changes * Minor flake8 fix * Fixing some issues * Fixed a weakref.ref issue * Fixed one more weakref issue * Fixed some issues with required version * Fixed more python min version requirements * More min version fixes * Fixed misc error in workflow regarded outdated pip * Replaced any usage of Optional and Union with proper form as described in the contributions guide * Fixed issue with using Callable definition * Fixed last seen issues as per review * Fixed some basic issues & more proper import calls * Update stdlib/concurrent/futures/process.pyi Co-authored-by: Sebastian Rittau <srittau@rittau.biz> * Update stdlib/concurrent/futures/process.pyi Co-authored-by: Sebastian Rittau <srittau@rittau.biz> * Minor fixes * More minor fixes * Fixed up some issues & cleaned up imports * Removed usage of Union * Changed wait method to use Set of Future to work with mypy-primer for Optuna repo * Reverted change to wait method and DoneAndNotDoneFutures class * Fixed DoneAndNotDoneFutures again Co-authored-by: Akuli <akuviljanen17@gmail.com> Co-authored-by: Sebastian Rittau <srittau@rittau.biz>
typeshed
About
Typeshed contains external type annotations for the Python standard library and Python builtins, as well as third party packages as contributed by people external to those projects.
This data can e.g. be used for static analysis, type checking or type inference.
For information on how to use typeshed, read below. Information for
contributors can be found in CONTRIBUTING.md. Please read
it before submitting pull requests; do not report issues with annotations to
the project the stubs are for, but instead report them here to typeshed.
Typeshed supports Python versions 2.7 and 3.6 and up.
Using
If you're just using mypy (or pytype or PyCharm), as opposed to
developing it, you don't need to interact with the typeshed repo at
all: a copy of standard library part of typeshed is bundled with mypy.
And type stubs for third party packages and modules you are using can
be installed from PyPI. For example, if you are using six and requests,
you can install the type stubs using
$ pip install types-six types-requests
These PyPI packages follow PEP 561 and are automatically generated by typeshed internal machinery. Also starting from version 0.900 mypy will provide an option to automatically install missing type stub packages (if found on PyPI).
PyCharm, pytype etc. work in a similar way, for more details see documentation for the type-checking tool you are using.
The _typeshed package
typeshed includes a package _typeshed as part of the standard library.
This package and its submodules contains utility types, but is not
available at runtime. For more information about how to use this package,
see the stdlib/_typeshed directory.
Discussion
If you've run into behavior in the type checker that suggests the type stubs for a given library are incorrect or incomplete, we want to hear from you!
Our main forum for discussion is the project's GitHub issue tracker. This is the right place to start a discussion of any of the above or most any other topic concerning the project.
If you have general questions about typing with Python, or you need a review of your type annotations or stubs outside of typeshed, head over to our discussion forum. For less formal discussion, try the typing chat room on gitter.im. Some typeshed maintainers are almost always present; feel free to find us there and we're happy to chat. Substantive technical discussion will be directed to the issue tracker.