-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Fix collections import warnings for Python 3.7 #11786
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
Conversation
damn, missed my chance to contribute again! One of these days ;) |
(btw, scikit-learn now raises deprecation warnings as errors during CI so that's where this is from) |
Sorry, didn't want to steal your contribution. Since nothing happend for some days and 3.0 is closing in, I worte the PR myself. Anyway, thanks a lot for the hint on the warnings. Also, there's still enough to contribute to matplotlib. We won't run out of topics for the time being 😄 . |
@meeseekdev backport to v2.2.x |
@meeseeksdev backport to v2.2.x |
There seem to be a conflict, please backport manually |
Fix collections import warnings for Python 3.7 Put try...except blocks in to support py27
…-v2.2.x Merge pull request #11786 from timhoffm/collections-abc
PR Summary
This is in continuation of #11733.
As @amueller pointed out on gitter, there were still some abstract base classes imported via
collections
instead ofcollections.abc
.