-
Notifications
You must be signed in to change notification settings - Fork 29.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
build,tools: Python3 compatibility and refactoring #26725
Conversation
/CC @nodejs/python @nodejs/build-files Still has a few bugs. But still PTAL. |
b7a3e11
to
36f93f6
Compare
1fcf092
to
aa3826a
Compare
Ping @nodejs/python |
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.
Is the new and empty tools/configure_lib/__init__.py
necessary?
try: | ||
from urllib.request import FancyURLopener | ||
except ImportError: | ||
from urllib import FancyURLopener, URLopener |
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.
URLopener
seems unused
It's a python thing (it tells the runtime that that directory is a "package") that enables doing: Lines 30 to 32 in 2fa8dc4
(which is not cricket) |
action='store_true', | ||
default=False, | ||
help='compile V8 with minimal optimizations and with runtime checks') | ||
parser.add_argument('extra_gyp_args', |
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.
This is not necessary for Python 3 compatibility I believe. Can you explain why this is introduced?
parser = argparse.ArgumentParser() | ||
shared_optgroup = parser.add_argument_group( | ||
"Shared libraries", | ||
"Flags that allows you to control whether you want to build against built-in dependencies" |
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.
Nit: There are a few lines which cross the 80 characters limit.
I feel that the refactoring can be done in a separate PR. Not introducing any new additional code would be easy for us to debug problems. |
aa3826a
to
9a8292e
Compare
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 with nits fixed and green CI
/cc @cclauss |
My vote would be that we close this. We have touched these files in the interim and most of these changes have been done. Is there anything remaining that we should consider? |
Refs: nodejs#26725 Fixes: nodejs#29813 Refs: nodejs#29814 PR-URL: nodejs#35755 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Christian Clauss <cclauss@me.com>
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes