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.

Sign up for GitHub

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

Jump to bottom

Dropping python 2 #120

Closed
timj opened this issue May 16, 2019 · 3 comments · Fixed by #153
Closed

Dropping python 2 #120

timj opened this issue May 16, 2019 · 3 comments · Fixed by #153
Milestone
v1.0

Comments

@timj
Copy link
Contributor

timj commented May 16, 2019

What's the timeline for dropping support for python 2? Python 2 formally dies in 2020 and Astropy dropped it long ago. Removing the six and __future__ code will make things a lot cleaner.

Should we issue a v1.0 on PyPI and drop python 2 after that?
@funbaker
Copy link
Contributor

Given that many projects still rely on 2, and that a release because of recent fixes is necessary, i agree.

@bsipocz
Copy link
Member

bsipocz commented May 23, 2019

The plan we agreed to last week was to release the last 0.3.x nowish, and them move on to 1.0 with the new features and removed python2 support.

@cbanek cbanek added this to the v1.0 milestone May 29, 2019
@hugovk hugovk mentioned this issue Jun 18, 2019
Merged
@hugovk
Copy link
Contributor

hugovk commented Jun 18, 2019

Please see PR #153.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v1.0
Development

Successfully merging a pull request may close this issue.

Drop support for legacy Python 2.7 hugovk/pyvo
5 participants
@timj @hugovk @bsipocz @funbaker @cbanek