build: update required python version to 3.8#54358
build: update required python version to 3.8#54358nodejs-github-bot merged 5 commits intonodejs:mainfrom
Conversation
Co-Authored-By: Jim B <d3x0r@users.noreply.github.com>
|
Instead of doing this over and over again, I would strongly recommend that we point readers to the currently supported versions as we do at https://github.com/nodejs/node-gyp/blob/main/README.md#on-unix |
I've made that change to the "Windows" section, but I think it's okay to keep the exact version in "Prerequisites". As for 3.12, I think that's an issue for a different PR, as this one is specifically removing up until 3.8, not adding more versions. |
|
@cclauss I noticed you π my comment, is there a specific part you'd like to be changed? It's also worth noting the 'missing' v3.12 is specificly for the android compilation. |
@cclauss What's the basis of blocking this pull request? I didn't understand. |
|
@cclauss ... The "did I stutter" comment here is unproductive, unfriendly, and unhelpful. If you are requesting changes to this PR please articulate what those are. |
My requested changes have already been stated. If you choose to ignore them then please proceed. My contributions to Node.js have been all about keeping its Python infrastructure current. My suggestions above are merely a continuation of that effort to ensure that Node.js users open fewer Python-related issues. |
|
I understand that you have requested changes. The issue is more the rather disrespectful way you presented your change request. The "did I stutter" comment was disrespectful. |
Trott
left a comment
There was a problem hiding this comment.
LGTM with or without changing android-configure to support 3.12 (and 3.13, just to be synchronized with configure) but I do have a slight preference that it be changed in this PR.
Co-authored-by: Christian Clauss <cclauss@me.com>
Co-authored-by: Christian Clauss <cclauss@me.com>
I'm sorry if you feel my response was disrespectful. I had no intention of it coming off that way.
I don't want you to think I'm ignoring your review comments. Your insight is extremely important.
I only marked one of your reviews as resolved, as I felt it would be easier to manage if there was one conversation rather than two going on about the same topic.
I'm happy to do the work required for android's configure script to support 3.12 and 3.13, I just don't believe that work should be done in this PR. |
|
I think we are all good @redyetidev. I do appreciate your work and I apologize for being snarky. I approved this PR so we can move forward... |
|
@redyetidev the red message below says Merging is blocked. |
I think that's what it says on all of our PRs. I think of it as a way to mostly make sure no one accidentally uses the GitHub button. |
Nope. That's why I immediately re-added them. Not sure how they all got de-selected. I might need my web-browsing license revoked. |
Happens to me more often that i can count... π |
|
Landed in 22daeba |
|
|
Co-Authored-By: Jim B <d3x0r@users.noreply.github.com> PR-URL: #54358 Reviewed-By: Christian Clauss <cclauss@me.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Co-Authored-By: Jim B <d3x0r@users.noreply.github.com> PR-URL: #54358 Reviewed-By: Christian Clauss <cclauss@me.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
|
Hey, I'm requesting this be back ported to v20 per the discussion in the v20.18.0 release proposal, feel free to adjust |
|
Python 3.8 goes EOL on Monday so let's stop supporting it. |
|
Okay. I'll update the required version to 3.12, but I think 3.8 is okay for v20 |
Please don't. We need some common denominator with the CI machines that are on non-EOL OS. |
|
After next Monday acceptable versions should be py39, py310, py311, py312, py313. With Python's new yearly (October) release approach, there should always be five supported versions of CPython. |
|
I've opened a PR to drop support for 3.8 (In my comment above, I said 3.12, I meant 3.9, not sure how I mixed up those two π€ ) |
Closes #54112