Remove fixes/compat for Python 2
See original GitHub issueThis can be broken up into multiple pull requests.
Remove:
-
from __future__
imports -
sklearn.externals.six
-
super(cls, self)
is nowsuper()
- any code explicitly commented to be for Python 2 support
- anything else in sklearn.utils.fixes related to this
Admittedly I’m not sure it is wise to rush this change, given that we might still be backporting fixes to 0.20.X for a little while…
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
How to uninstall Python 2.7 on a Mac OS X 10.6.4?
I want to completely remove Python 2.7 from my Mac OS X 10.6.4. I managed to remove the entry from the PATH variable...
Read more >Sunsetting Python 2
We are volunteers who make and take care of the Python programming language. We have decided that January 1, 2020, was the day...
Read more >Remove support for python2 · Issue #7198 · emscripten-core ...
MacOS has Python2 built in, but not Python3. Python2 may be removed at some point. · The emsdk ships python 2.7 for windows....
Read more >How to remove Python 2 from Ubuntu 20.04?
I've upgraded recently from Ubuntu 18.04 to 20.04. But I can see that Python2 is still the default instead of python 3.8.2. $...
Read more >Changes/F31 Mass Python 2 Package Removal - Fedora
Retire python2-only packages; Remove python2 subpackages from dual-python packages; Break python2-only dependencies; File bugs to request and ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I also can’t wait for this to happen, but I think we might want to wait for the final 0.20.0 release or even 0.20.1 before removing Py2 code to make backports easier.
I think all of the points were indeed addressed here.
@albertvillanova thanks! If you are looking for for another issue to contribute, you can also have a look at stalled PRs starting with those that are short and not too controversial as they are more likely to get merged faster.