-
Notifications
You must be signed in to change notification settings - Fork 37
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
Drop Support for Python 3.5 #340
Conversation
Codecov Report
@@ Coverage Diff @@
## master #340 +/- ##
==========================================
- Coverage 76.24% 76.22% -0.03%
==========================================
Files 43 43
Lines 7103 7096 -7
==========================================
- Hits 5416 5409 -7
Misses 1687 1687
Continue to review full report at Codecov.
|
@vishav1771 I also searched the codebase and found a couple things you might have missed: signac/signac/contrib/import_export.py Line 546 in 842a07f
signac/signac/contrib/collection.py Line 925 in 842a07f
I found these by searching the codebase for Please also remove these outdated conda testing scripts, since we no longer support any Python version listed in them. 😆
Otherwise this looks good to me! I'll let @atravitz and @jennyfothergill review/approve/finalize. Thanks. 👍 |
Are we planning to have no releases anymore before EOL Py3.5? Then this should not go into master. I think that in general there should be a discussion over the supported Python minor versions. |
@csadorf I may have misunderstood your comment earlier that prompted this - I thought you were in support of dropping 3.5 because. EOL is soon, but we could make one more release if you think it is necessary. Let’s discuss adhering to NEP 29, which I linked on the other discussion. |
My other comment was targeted to ensure that we don't expand efforts to support Py 35 for that specific feature development. I might have missed the other discussion. I think sticking to NEP 29 is a very good idea, but we should make that explicit somewhere. Support/non-support for Python versions must be handled very transparently both for users and developers IMO. |
Dropping python3.5 will let us update pandas to the 1.x line, but I do think we need a more discussion about what the last release will be to support python3.5 |
Following our dev meeting discussion on Monday, I will update this PR to document that we follow NEP 29. I think that is best done in the same PR but let me know if you disagree. |
That's fine, no need to over-engineer. |
I have updated this PR to document that we now follow NEP 29. @atravitz @jennyfothergill @csadorf I think it's ready for review. Thanks for this contribution @vishav1771! |
Reviewers: ignore the failing test on pypy. This will be handled after this PR and #341 are merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have reviewed and approve this PR.
Description
This PR drops support for Python 3.5. I have removed CI tests, updated do and updated setup.py
Motivation and Context
#336
Types of Changes
1The change breaks (or has the potential to break) existing functionality.
Checklist:
If necessary:
Example for a changelog entry:
Fix issue with launching rockets to the moon (#101, #212).