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

Drop Support for Python 3.5 #340

Merged
merged 4 commits into from
Jul 6, 2020
Merged

Drop Support for Python 3.5 #340

merged 4 commits into from
Jul 6, 2020

Conversation

vishav1771
Copy link
Contributor

@vishav1771 vishav1771 commented Jun 19, 2020

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

  • Documentation update
  • Bug fix
  • New feature
  • Breaking change1

1The change breaks (or has the potential to break) existing functionality.

Checklist:

If necessary:

  • I have updated the API documentation as part of the package doc-strings.
  • I have created a separate pull request to update the framework documentation on signac-docs and linked it here.
  • I have updated the changelog and added all related issue and pull request numbers for future reference (if applicable). See example below.

Example for a changelog entry: Fix issue with launching rockets to the moon (#101, #212).

@vishav1771 vishav1771 requested review from a team as code owners June 19, 2020 12:07
@vishav1771 vishav1771 requested review from atravitz and jennyfothergill and removed request for a team June 19, 2020 12:07
@codecov
Copy link

codecov bot commented Jun 19, 2020

Codecov Report

Merging #340 into master will decrease coverage by 0.02%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            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              
Impacted Files Coverage Δ
signac/contrib/collection.py 88.97% <100.00%> (-0.09%) ⬇️
signac/contrib/import_export.py 84.63% <100.00%> (-0.13%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 842a07f...72ede7a. Read the comment docs.

@bdice
Copy link
Member

bdice commented Jun 19, 2020

@vishav1771 I also searched the codebase and found a couple things you might have missed:

if sys.version_info < (3, 6):

if sys.version_info < (3, 6):

I found these by searching the codebase for version and 3.*6 and 3.*5 and filtering non-matches.

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. 👍

@csadorf
Copy link
Contributor

csadorf commented Jun 19, 2020

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 csadorf self-requested a review June 19, 2020 15:28
@bdice
Copy link
Member

bdice commented Jun 19, 2020

@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.

@csadorf
Copy link
Contributor

csadorf commented Jun 19, 2020

@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.

@mikemhenry
Copy link
Collaborator

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

@bdice
Copy link
Member

bdice commented Jun 24, 2020

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.

@bdice bdice mentioned this pull request Jun 24, 2020
12 tasks
@csadorf
Copy link
Contributor

csadorf commented Jun 24, 2020

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.

@bdice
Copy link
Member

bdice commented Jun 25, 2020

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!

@bdice bdice added this to the v1.5.0 milestone Jun 25, 2020
@bdice bdice added enhancement New feature or request GSoC Google Summer of Code labels Jun 25, 2020
@bdice
Copy link
Member

bdice commented Jun 25, 2020

Reviewers: ignore the failing test on pypy. This will be handled after this PR and #341 are merged.

@bdice bdice self-assigned this Jun 28, 2020
Copy link
Member

@bdice bdice left a 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.

@bdice bdice merged commit 2044a76 into master Jul 6, 2020
@bdice bdice deleted the drop_py3.5 branch July 6, 2020 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request GSoC Google Summer of Code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants