-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Make Python 2 and 3 concurrent.futures stubs identical #2234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
li-dan
pushed a commit
to li-dan/typeshed
that referenced
this issue
Jun 15, 2018
Make the Python 2 and 3 concurrent.futures stubs identical so fixes get applied to both. For example, python#1305 and python#2233 fixed the same problem at differnt times, as did python#1078 and python#1911. By making the stubs identical, we apply the fix from python#1711 to Python 2. Fixes python#2234.
li-dan
pushed a commit
to li-dan/typeshed
that referenced
this issue
Jun 15, 2018
Make the Python 2 and 3 concurrent.futures stubs identical so fixes get applied to both. For example, python#1305 and python#2233 fixed the same problem at different times, as did python#1078 and python#1911. By making the stubs identical, we apply the fix from python#1711 to Python 2. Fixes python#2234.
yedpodtrzitko
pushed a commit
to yedpodtrzitko/typeshed
that referenced
this issue
Jan 23, 2019
Make the Python 2 and 3 concurrent.futures stubs identical so fixes get applied to both. For example, python#1305 and python#2233 fixed the same problem at different times, as did python#1078 and python#1911. By making the stubs identical, we apply the fix from python#1711 to Python 2. Fixes python#2234.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This should be doable; see #2233.
The advantage is that we'd be able to ensure that improvements to one of the two copies also make it to the other.
The text was updated successfully, but these errors were encountered: