Skip to content

Conversation

bsamuel-ui
Copy link
Contributor

Description

This drops python 2.7 support from the tests.

It further updates the README to explain the situation. While we're not explicitly breaking 2.7 support, we're no longer enforcing it, so this requires a major version increment per semver.

Scanning through the codebase, there's no conditional logic to support python 2.7 that I could find. And that makes sense: we delegate to tools that provide 2.7 support. So, most likely, if someone wanted to use the plugin with an older pip, it would Just Work.

I'm also proposing that we reject future fixes that require conditional logic; given that we have none now and those would be quite gory, I don't think this will matter much, but it does lay out the practical implications of dropping support.

Testing

Not much to do here beyond making sure the test suite runs correctly.

@bsamuel-ui bsamuel-ui marked this pull request as ready for review April 12, 2021 05:04
miketheman
miketheman previously approved these changes Apr 14, 2021
Copy link
Contributor

@miketheman miketheman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay! Thanks for taking this up. I'm in favor of dumping 2.7 post-haste.

3.6 is EOL at the end of this year, so we also probably want to start thinking about 3.7 and higher.
https://endoflife.date/python

@pgrzesik
Copy link
Contributor

Hey @bsamuel-ui - I'm going to close this PR - I'm currently in process of updating the supported versions, so I'll handle droping Python 2.7 in future PRs. Thanks 🙇

@pgrzesik pgrzesik closed this Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants