Skip to content
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

Possible python version bug, during build on MacOS High Sierra #22353

Closed
SirR4T opened this issue Aug 16, 2018 · 5 comments
Closed

Possible python version bug, during build on MacOS High Sierra #22353

SirR4T opened this issue Aug 16, 2018 · 5 comments
Labels
wrong repo Issues that should be opened in another repository.

Comments

@SirR4T
Copy link
Contributor

SirR4T commented Aug 16, 2018

  • Version: v8.11.3
  • Platform: Darwin hostname.local 17.7.0 Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64 x86_64
  • Subsystem: build

When running make -j8 after pulling the latest upstream master, I sometimes see this error:


  File "../third_party/inspector_protocol/CheckProtocolCompatibility.py", line 470
    print "  Public changes since %s:" % version
                                     ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("  Public changes since %s:" % version)?
make[1]: *** [/Users/saratchandra/Play/Github/nodejs/node/out/Release/obj/gen/src/js_protocol.stamp] Error 1
make[1]: *** Waiting for unfinished jobs....
Failed to parse command-line arguments: 'str' object has no attribute 'decode'

Failed to parse command-line arguments: 'str' object has no attribute 'decode'

make[1]: *** [7f4282a28ceb040a63a7982b4d396ec51b11796f.intermediate] Error 1
make[1]: *** [463be0202ecca11b345bd9ea2e1944ad6f917b33.intermediate] Error 1
rm 2be2316469838db878135dc7e59cb5f41a42f3a7.intermediate 7f4282a28ceb040a63a7982b4d396ec51b11796f.intermediate 463be0202ecca11b345bd9ea2e1944ad6f917b33.intermediate
make: *** [node] Error 2

This seems to get fixed when running ./configure and make -j8 again, though.

@richardlau
Copy link
Member

That SyntaxError is typical of trying to run with Python 3.

@SirR4T
Copy link
Contributor Author

SirR4T commented Aug 16, 2018

ok, But i hadn't changed my python version. So the build system is able to pick up the python2 executable (I have both python versions installed, via homebrew), but it does so only after running ./configure.

Shouldn't the python executable's path be encoded somewhere, so that subsequent make -j8 runs do not attempt to use python 3 instead?

@richardlau
Copy link
Member

The configure script was patched in #14737 to handle the situation where python is Python 3 but this doesn't apply to invocations of python in the gyp scripts, e.g.

'python',
'<(protocol_path)/CheckProtocolCompatibility.py',
'--stamp', '<@(_outputs)',
'<(inspector_path)/js_protocol.json',

@Trott Trott added the python PRs and issues that require attention from people who are familiar with Python. label Nov 18, 2018
@Trott
Copy link
Member

Trott commented Nov 18, 2018

@nodejs/python @nodejs/gyp Worth fixing somehow? Or should this be closed as wont-fix?

@refack
Copy link
Contributor

refack commented Nov 18, 2018

First it should be reported upstream at https://chromium.googlesource.com/deps/inspector_protocol.
Second this will be solved withhttps://github.com//issues/23659

I'm going to close this as wrong repo

@refack refack closed this as completed Nov 18, 2018
@refack refack added wrong repo Issues that should be opened in another repository. and removed python PRs and issues that require attention from people who are familiar with Python. labels Nov 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wrong repo Issues that should be opened in another repository.
Projects
None yet
Development

No branches or pull requests

4 participants