You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Python2.7 is already an issue with the liac-arff package, where the latest version on pypi doesn't support python2.7 completely (see #45). Dropping python2.7 probably wouldn't hurt anyone, but make maintenance for us easier. @amueller what do you think?
@amueller given your recent sckit-learn issue on this, do you think we can drop python2.7 support now? This would make some pieces of code easier and potentially allow us to use type hints to improve code quality.
Activity
amueller commentedon Nov 11, 2016
No, I think we should keep it.
amueller commentedon Nov 11, 2016
Sorry I have so many meetings at my new job right now and I get nothing done :-/
mfeurer commentedon Nov 11, 2016
No worries. But could you elaborate for which projects/whom it would be beneficial to keep python2 support?
amueller commentedon Nov 11, 2016
unfortunately many many people are still working with python2.7. And upgrading an existing piece of code is not always trivial.
mfeurer commentedon Nov 11, 2016
I agree about the second part. But is this also true in academia?
amueller commentedon Nov 11, 2016
yes, totally!
mfeurer commentedon Nov 11, 2016
Okay :(
mfeurer commentedon Jun 14, 2018
@amueller given your recent sckit-learn issue on this, do you think we can drop python2.7 support now? This would make some pieces of code easier and potentially allow us to use type hints to improve code quality.
mfeurer commentedon Sep 20, 2018
@amueller ping
mfeurer commentedon Feb 25, 2019
Closed via #623