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 Python 2.7 support #476

Closed
nitzmahone opened this issue Jan 14, 2021 · 2 comments
Closed

Drop Python 2.7 support #476

nitzmahone opened this issue Jan 14, 2021 · 2 comments

Comments

@nitzmahone
Copy link
Member

PyYAML 5.4 is the last planned release with Python 2.7 support. With 5.4's conversion to setuptools, the python_requires metadata is now being properly generated into the sdists and indexed by PyPI, so Python 2.7 users will be properly directed to a 5.4 release by, eg, pip install pyyaml without needing to pin a version.

Dropping 2.x support will allow us to remove the bifurcated 2.x/3.x codebase- a significant maintenance hassle, as well as simplifying the Windows wheel builds (making them easier to migrate to GHA for a single CI platform).

If major bugs/security/whatever issues are found, we've not ruled out the possibility of doing additional patch releases on the 5.4 codebase, but those would be evaluated case-by-case if/when they happen.

@ingydotnet
Copy link
Member

@Thom1729 You should start by removing lib/ and tests/lib and any file references to them.

Then make sure tests run.

Then rename **lib3 to lib and all refs etc, and get tests passing.

Please target any PRs against the release/6.0 branch.

@ingydotnet ingydotnet moved this from To Do to Assigned in PyYAML 6.0 Release Planning Sep 2, 2021
@Thom1729 Thom1729 moved this from Assigned to Done in PyYAML 6.0 Release Planning Sep 22, 2021
@Thom1729 Thom1729 moved this from Done to Assigned in PyYAML 6.0 Release Planning Sep 22, 2021
@Thom1729 Thom1729 moved this from Assigned to Done in PyYAML 6.0 Release Planning Sep 22, 2021
@nitzmahone
Copy link
Member Author

implemented by #550

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

3 participants