-
Notifications
You must be signed in to change notification settings - Fork 242
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
_abc_registry errors with py3.8 #721
Comments
Hm, with Python 3.8, typing.py should not come from site-packages. This seems to point to some installation or configuration error on your part. Please seek help elsewhere. |
I'm on python 3.7 and latest pip and recently started getting this error. My solution was to remove typings. Is there a better solution?
|
The solution is probably |
This worked. Any idea why this might happen all of a sudden? |
Maybe you or a script incorrectly ran 'pip install typing'. Or maybe some other thing that you installed had an incorrect dependency on typing. It would require a lot of research to find out what happened, and it would have to be done on your computer. I haven't heard of this before (other than the initial report in this issue). |
I wonder if there's a way to make this package refuse to install itself on any Python version that has a typing module in the stdlib. (I think starting with 3.5.) |
The Line 70 in 08a537d
It was changed in #722, and it seems you proposed disallowing installation on 3.5+. Seeing as all versions of Python 3 that don't have typing in the stdlib are not longer supported themselves, I guess the pypi package only has use for 2.7? |
2.7 is also unsupported now, though clearly it's still being used a lot. Some projects also decide to continue to support unsupported Python 3 versions. For a very widely used package such as |
Maybe the right thing to do is just not to do any new releases of the |
Is that true for typing tools in general? I believe typeshed for example should still accept Python 2.7 fixes. |
Yeah, typeshed still supports 2.7. I meant that CPython 2.7 has reached it's End of Life. (Tangentially related: even if typeshed doesn't support older 3.x releases officially, more recent 3.x stubs generally work just fine with older Python 3 releases.) |
Would releasing a new version of |
I could do that, if @JukkaL and/or @ilevkivskyi agree that now's a good time. |
Yes, thanks, this is a good time. |
This is the right answer |
@maxwellmckinnon I'm still a wheels newbie. Do you know how to do that from a wheel? |
Never mind the answer is a few comments up. |
Okay, I've done a release of typing 3.7.4.2. I changed python_requirements so that it only installs on 2.7 and 3.4. I couldn't find an installable binary of 3.4 (it's well out of support) so I only tested on 2.7 -- if anyone is still using 3.4 and finds a problem they know where to find us. For this reason there also isn't a wheel for 3.4, only an sdist. The changes I made to setup.py are now in master and tagged "3.7.4.2". |
FWIW, there were complaints about the version restrictions I applied (last minute) to 3.7.4.2, so I've released 3.7.4.3 which undoes that (but is otherwise the same). There's still no py3 wheel. |
The text was updated successfully, but these errors were encountered: