-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
gyp: pull Python 3 changes from node/node-gyp #28573
Conversation
@nodejs/python @nodejs/gyp |
@MattIPv4 You review of these changes please. |
@cclauss What is the aim with this? Is support for 2.7 intended still, or is this a complete move to 3.x? |
Both Python and legacy Python must be supported. |
@cclauss Is legacy Python simply regarded as 2.7 now and not older versions that were supported before? |
Yes. See BUILDING.md. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lgtm.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
RSLGTM
Since this drops support Python 2.6 and below I labelled it dont-land
10.x and 8.x, which document support for 2.6 in their BUILDING.md. Someone can correct that if I misunderstand.
AFAICT, there is a bug in core-validate-commit, see nodejs/core-validate-commit#65
You could use tools:
as a sub-system to make Travis happy, it can be patched if necessary when this is landed.
@nodejs/gyp Needs one more approval to land (or will have to wait 114 more hours...). @cclauss FYI, your github profile and your commit lack identifying information. Its not absolutely required, but it is helpful to be able to attribute commits to specific humans.
|
How do we make progress on this? Are there any Pythonistas in the project that we should add as reviewers? @nodejs/python |
@bnoordhuis You may be the sole member of https://github.com/orgs/nodejs/teams/gyp that is still active on the project, PTAL |
brace_diff = 0 | ||
if not COMMENT_RE.match(line): | ||
if COMMENT_RE.match(line): | ||
print(line) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this not change the behavior? Before, it used to strip '\r\n\t ' from the line?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this is still doing that at 126 - This just now prints the line if it matches the regex, otherwise strips - Unlike before where it stripped it if failed the regex immediately.
PR-URL: nodejs#28573 Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Landed in 5ebaf70 |
PR-URL: #28573 Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
PR-URL: nodejs#28573 Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> (cherry picked from commit 5ebaf70)
#28563 is too complicated for easy review. It touches 32 files some of which contain complex changes. This PR is a subset of #28563 which brings across 16 files (the easy half) that only contain Python 3 compatibility modifications. Once this PR is merged, we can rebase #28563 and focus our attention on the complex half.
The commands used to create this PR are below...
Order of execution: This PR (#28573), then #28563, then #28537, then #25878
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes