-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Remove python 2.7 as requirement from the README.md #2052
Comments
Is the |
Yeah, it's still on 5.0.5 and unfortunately people are still directed here for details on what to install with native addons. Maybe once we get npm out with ^5.1.0 we can start being more aggressive with our README? |
Sounds like a plan, I've filed a feature request over on the npm issue tracker to bump that version to at least 5.1.0 . |
My bet is that this would be SemVer Major. At what stage would it intersect |
It doesn't? At least so far Release has not been involved with node-gyp. |
Not directly, but they'd have to decide whether an updated I've filed nodejs/Release#538 for that purpose. |
A correction on the timeline, I missed the fact that a press release late last December pushed the EOL date back to April 1st, so there's a few more weeks left before Python 2.7 is well and truly dead. |
@Pomax Actually no. EOL already happened on January 1. Development of Python 2.7 already stopped. PSF already stopped providing official support. However, the last release will be in April, but EOL is still on January 1. |
The "bible" of these things is... |
Even better, thank you. |
|
#2300 removed Python 2 support. |
Python 2.7 is dead. No "if"s, no "but"s, no "we're keeping it around because...": it's well and truly dead,
Given that it got killed on January first, 2020, which is nearing two months ago, can we remove it from the README.md as a valid requirement? (as well as everywhere else it's still being referenced?)
The text was updated successfully, but these errors were encountered: