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

Make next release 3.6+? #51

Closed
IAlibay opened this issue Jul 20, 2021 · 2 comments · Fixed by #61
Closed

Make next release 3.6+? #51

IAlibay opened this issue Jul 20, 2021 · 2 comments · Fixed by #61

Comments

@IAlibay
Copy link
Member

IAlibay commented Jul 20, 2021

Mainly looking at this because of #48, supporting py2.7/py3.5 (if just the act of conda installing an environment) is becoming increasingly tedious.

Given that MDA 2.0 will be py3.6+ and that 2.7 has now long been deprecated, would it be worth making MDAnalysisData's python 3.6->3.9?
@orbeckst
Copy link
Member

orbeckst commented Oct 1, 2021

We can... but it also works with the old stuff, according to the tests in PR #52 . (It would have required a bit less duct-taping in the tests if I could have ignored 2.7 but the bigger issue was UNIX vs Windows.)

I want to cut a quick 0.8.1 #53 with legacy included and then we have a firm foundation if we want to drop legacy.

@orbeckst orbeckst linked a pull request Oct 29, 2023 that will close this issue
Try to modernise package a bit #61
Merged
@orbeckst
Copy link
Member

Went NEP29-ish with PR #61 so this is done.

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
No milestone
Development

Successfully merging a pull request may close this issue.

Try to modernise package a bit MDAnalysis/MDAnalysisData
2 participants
@orbeckst @IAlibay