-
Notifications
You must be signed in to change notification settings - Fork 0
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
Remove duplication in typing backports? #3
Comments
It's kinda strange that typing exists. It masks a stdlib module, so if you install it on Python 3, you still get the stdlib version when But if that's the recommended way to provide cross-version compatibility, then there's no need for backports. So be it. |
I've removed it from PyPI. |
@jaraco removing |
@enkidulan, you should just move to using |
@ethanhs I'm using I don't really see why removing |
Since gvr requested it be removed, I found it difficult to argue. I presume by now the damage is done, but if you wish to re-publish backports.typing (perhaps with the deprecation warning), feel free to register and upload the dists. If you would like me to hand over this repo to your account, I'm happy to do that too. |
That is scary :) I'm willing to contribute to making deprecation procedure of |
Hello,
I am a collaborator on mypy. We recently came across someone who was using this package with mypy, and it was causing issues. The problem was trying to use
backports.typing.{type}
as a valid type. Since there is already thetyping
module and backport, I was interested in the possibility of removing this package from PyPI, and pointing to the official backport when the user tries to install it. That way confusion is avoided and everyone can use the official typing. You can see the context and the issue here. Thanks!Ethan
The text was updated successfully, but these errors were encountered: