[go: nahoru, domu]
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

Python 2.7/3.4 Support #23

Closed
miketheman opened this issue Feb 9, 2019 · 3 comments
Closed

Python 2.7/3.4 Support #23

miketheman opened this issue Feb 9, 2019 · 3 comments
Labels
more-info-needed Further information is requested

Comments

@miketheman
Copy link
Owner

Following #21 and associated fix in #22 to accommodate a Python 2.7 behavior, I started thinking about when this plugin should stop supporting Python 2.7 / 3.4

According to the https://pythonclock.org/ , support ends at the end of 2019.

pytest has started warning about deprecation:

You are using Python 2.7.15, which will no longer be supported in pytest 5.0

pytest 5.0 is scheduled for sometime mid-2019 - after which the pytest 4.x branch will continue to be supported until mid-2020.

Please use this issue to discuss your use cases and expectations for longer-term support if you're looking for those versions to be supported beyond the runtime and test framework's lifetime.
@miketheman miketheman added the more-info-needed Further information is requested label Feb 9, 2019
@miketheman
Copy link
Owner Author
miketheman commented Nov 2, 2019 •
edited
Loading

Today I learned of this nice visual representation of the lifecycle: https://python-release-cycle.glitch.me/
So I think it's safe to consider that support for 2.7 and 3.4 can be removed any time now.

@atugushev
Copy link
Contributor
atugushev commented Nov 2, 2019 •
edited
Loading

The 3.4 has been dropped by many projects since April. The 2.7 better to drop after 01.01.2020.

@miketheman
Copy link
Owner Author
miketheman commented Apr 9, 2020 •
edited
Loading

Today I noticed that Python 3.4 no longer works with pip version 20.x and fails the Appveyor build.

Things I'm going to consider:

  • Migrate from TravisCI & AppVeyor to GitHub Actions for Linux, Windows, and add Mac
  • Drop support for Python 2.7, 3.4 (3.4 hit EOL over a year ago)
  • Remove tox from the equation and use the base pytest command
  • Add test support for Python 3.8, maybe 3.9, maybe pypy (See pypy3 hangs on threading #20 )
  • Convert project to use poetry for build/release tooling - no impact to end users

After a few of these things are done, I'll close out this issue, and get back to triage/testing the rest of the open issues.

@miketheman miketheman pinned this issue Apr 9, 2020
miketheman added a commit that referenced this issue Apr 10, 2020
@miketheman
chore: remove python 2 specific handling
fe9675f 
Refs: #23

Signed-off-by: Mike Fiedler <miketheman@gmail.com>
@miketheman miketheman mentioned this issue Apr 10, 2020
Merged
miketheman added a commit that referenced this issue Apr 10, 2020
@miketheman
chore: remove python 2 specific handling
bd84412 
Refs: #23

Signed-off-by: Mike Fiedler <miketheman@gmail.com>
@miketheman miketheman unpinned this issue Apr 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
more-info-needed Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@miketheman @atugushev