Deprecate support for EOL Python versions on MacOS
See original GitHub issueSummary
PR #79 introduces GitHub actions for performing CI/CD. The pipeline executes the test suite across all supported Python versions on multiple operating systems.
actions/virtual-environments#4060 updates the macOS-latest
workflow to reference macOS-11
(from macOS-10.5
); this is expected to remove support for Python versions 2.7
, 3.5
, and 3.6
. Accordingly, the GitHub actions configuration must be updated to accommodate this change.
Definition of Done
- CI tests for
macOS
are skipped/allowed to fail/expected to fail for Python2.7
,3.5
, and3.6
on macOS
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
What's the plan for Python on macOS following EOL in 2020?
A future version of pip will drop support for Python 2.7. Is there a plan in place to update the default version for...
Read more >Sunsetting Python 2
As of January 1st, 2020 no new bug reports, fixes, or changes will be made to Python 2, and Python 2 is no...
Read more >Apple removing Python 2.7 on Mac - What does this mean ...
Hence, in June 2019, Apple announced it was deprecating the Python 2.7 programming language and in April 2022, they removed support for Python...
Read more >macOS Monterey 12.3 will remove Python 2.7 (/usr/bin ...
macOS Monterey 12.3 will remove Python 2.7 (/usr/bin/python) ... Hot on the heels of macOS Monterey 12.2, Apple have publicly released the macOS...
Read more >How to Secure Python 2 Past End of Life (EOL) with ...
The Python 2 programming language is no longer supported by the Python Software Foundation (PSF). As such, the majority of third-party packages ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@jshwi I wouldn’t think so. In an ideal world, nobody uses 2.7 anymore, so the change would not have any impact. In a real world, anyone who is still running 2.7 is unlikely to install updates/upgrades to dependencies (especially since
pip
no longer supports 2.7)@bryant-finney Well there won’t be any more security patches etc for 2.7, so phasing it out should certainly be on the roadmap. Possible to just announce a deprecation warning up until the next minor release of this package.
Would you know if removing 2.7 would be considered a breaking change (3.xx -> 4.x.x)?