Skip to content
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

Plan for dropping Python 2 support. #1731

Closed
arokem opened this issue Feb 4, 2019 · 9 comments

Comments

@arokem
Copy link
Member

commented Feb 4, 2019

Description

Many software projects in the scientific python ecosystem are moving to require Python 3 for their usage. For example, both numpy and scipy have made their last releases to support Python 2. Though they both have plans for long-term support of Python 2 through 2020, it seems that after the end of next year, we would be on our own.

Proposed course of action

I propose that we consider making our current release cycle the last to provide full support for Python 2.7. The next release cycle would then drop the Python 2 bots, but we would continue long-term support through a maintenance branch and by back-porting crucial fixes through 2020. At that point, users who want to continue using Python 2 would be on their own. Given the movements in the rest of the scientific Python ecosystem, these users would need to be particularly hardy anway.

Thoughts?

@jchoude

This comment has been minimized.

Copy link
Contributor

commented Feb 4, 2019

I fully approve this!

@arokem

This comment has been minimized.

Copy link
Member Author

commented Feb 4, 2019

Just to add: one main thing we should think about here is what kind of effort LTS for Python 2 through 2020 would require, and whether it's worth it. Our conda download numbers do suggest that some users are getting it for their Python 2 installations, but we don't know whether they would just switch if we nudged them more firmly.

@skoudoro

This comment has been minimized.

Copy link
Member

commented Feb 4, 2019

+1, Since we plan to bump the major version to DIPY 1.0.0 this year, I think this a good opportunity

@jchoude

This comment has been minimized.

Copy link
Contributor

commented Feb 4, 2019

I know that I, for one, still get the Python 2 version by default, since our labs common setup uses that. We are already working on migrating the internal tools based on Python 2.7 to Python 3, so that would be one more incentive.

@arokem

This comment has been minimized.

Copy link
Member Author

commented Feb 4, 2019

@arokem

This comment has been minimized.

Copy link
Member Author

commented Feb 4, 2019

@skoudoro : yes, 1.0 would be a very clean point to do this.

Is that slated for the release after the upcoming one?

@arokem

This comment has been minimized.

Copy link
Member Author

commented Mar 2, 2019

BTW, looks like nibabel is planning to drop support for Python 2 as early as January 2020 (nipy/nibabel#735)

@skoudoro

This comment has been minimized.

Copy link
Member

commented Mar 5, 2019

Is that slated for the release after the upcoming one?

yes, it will be, end of June / begin July

@skoudoro skoudoro added this to the 1.0 milestone Apr 23, 2019

@skoudoro skoudoro pinned this issue May 15, 2019

@arokem

This comment has been minimized.

Copy link
Member Author

commented Jun 12, 2019

Resolved by #1775

@arokem arokem closed this Jun 12, 2019

@arokem arokem unpinned this issue Jun 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.