Still need Python2 to run node-gyp v5.0.3

[HanqingTony]

Still need python2, i don't know why. i installed node-gyp with python 3.73

C:\Windows\system32> npm install -g node-gyp
C:\Users\81810\AppData\Roaming\npm\node-gyp -> C:\Users\81810\AppData\Roaming\npm\node_modules\node-gyp\bin\node-gyp.js
+ node-gyp@6.0.1
updated 1 package in 9.504s
PS C:\Windows\system32> npm install -g ffi

> ref@1.3.5 install C:\Users\81810\AppData\Roaming\npm\node_modules\ffi\node_modules\ref
> node-gyp rebuild


C:\Users\81810\AppData\Roaming\npm\node_modules\ffi\node_modules\ref>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
gyp ERR! find Python
gyp ERR! find Python Python is not set from command line or npm configuration
gyp ERR! find Python Python is not set from environment variable PYTHON
gyp ERR! find Python checking if "python" can be used
gyp ERR! find Python - executable path is "C:\Program Files\Python37\python.exe"
gyp ERR! find Python - version is "3.7.3"
gyp ERR! find Python - version is 3.7.3 - should be >=2.6.0 <3.0.0
gyp ERR! find Python - THIS VERSION OF PYTHON IS NOT SUPPORTED
gyp ERR! find Python checking if "python2" can be used
gyp ERR! find Python - "python2" is not in PATH or produced an error
gyp ERR! find Python checking if the py launcher can be used to find Python 2
gyp ERR! find Python - "py.exe" is not in PATH or produced an error
gyp ERR! find Python checking if Python is C:\Python27\python.exe
gyp ERR! find Python - "C:\Python27\python.exe" could not be run
gyp ERR! find Python checking if Python is C:\Python37\python.exe
gyp ERR! find Python - "C:\Python37\python.exe" could not be run
gyp ERR! find Python
gyp ERR! find Python **********************************************************
gyp ERR! find Python You need to install the latest version of Python 2.7.
gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
gyp ERR! find Python you can try one of the following options:
gyp ERR! find Python - Use the switch --python="C:\Path\To\python.exe"
gyp ERR! find Python   (accepted by both node-gyp and npm)
gyp ERR! find Python - Set the environment variable PYTHON
gyp ERR! find Python - Set the npm configuration variable python:
gyp ERR! find Python   npm config set python "C:\Path\To\python.exe"
gyp ERR! find Python For more information consult the documentation at:
gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
gyp ERR! find Python **********************************************************
gyp ERR! find Python
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Python installation to use
gyp ERR! stack     at PythonFinder.fail (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:303:47)
gyp ERR! stack     at PythonFinder.runChecks (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:132:21)
gyp ERR! stack     at PythonFinder.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:221:16)
gyp ERR! stack     at PythonFinder.execFileCallback (C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\find-python.js:267:16)
gyp ERR! stack     at exithandler (child_process.js:302:5)
gyp ERR! stack     at ChildProcess.errorhandler (child_process.js:314:5)
gyp ERR! stack     at ChildProcess.emit (events.js:209:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:270:12)
gyp ERR! stack     at onErrorNT (internal/child_process.js:456:16)
gyp ERR! stack     at processTicksAndRejections (internal/process/task_queues.js:80:21)
gyp ERR! System Windows_NT 10.0.18362
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\81810\AppData\Roaming\npm\node_modules\ffi\node_modules\ref
gyp ERR! node -v v12.10.0
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ref@1.3.5 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ref@1.3.5 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\81810\AppData\Roaming\npm-cache\_logs\2019-11-24T23_02_43_511Z-debug.log
PS C:\Windows\system32>

[cclauss]

gyp ERR! node -v v12.10.0
gyp ERR! node-gyp -v v5.0.3

C:\Users\81810\AppData\Roaming\npm\node_modules\node-gyp\bin\node-gyp.js is node-gyp@6.0.1
C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js is node-gyp@5.0.3

[joaocgreis]

@HanqingTony please update npm:

npm install -g npm

[johnhoj]

Hi there,

I had a similar issue. I upgraded to OSX Catalina. Then when doing node-gyp build I got the error as in below. I realised Catalina does not take the old 32 bit python previously installed, so I installed Python3. However, even after changing the alias for python, verifying PATH and even enforcing node-gyp build --python=(python3path), it seemed as if node-gyp was still looking for python v2.

The solution was to reinstall python2 for 64 bits.

% node-gyp build
gyp info it worked if it ends with ok
gyp info using node-gyp@6.0.1
gyp info using node@10.16.2 | darwin | x64
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
LIBTOOL-STATIC Release/scrypt_wrapper.a
env: python: Bad CPU type in executable
make: *** [Release/scrypt_wrapper.a] Error 126
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/Users/john/.nvm/versions/node/v10.16.2/lib/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Darwin 19.0.0
gyp ERR! command "/Users/john/.nvm/versions/node/v10.16.2/bin/node" "/Users/john/.nvm/versions/node/v10.16.2/bin/node-gyp" "build"
gyp ERR! cwd /Users/john/dev/eth-test-embark/node-scrypt
gyp ERR! node -v v10.16.2
gyp ERR! node-gyp -v v6.0.1
gyp ERR! not ok

[codler]

I have the same issue

[Paulsky]

Please look at this article from 2019: https://spin.atomicobject.com/2019/03/27/node-gyp-windows/

On Windows, you have to use Python 2.7 and Microsoft Visual Studio 2015:

• Python 2.7: 'Python 2.7.0 was released on July 3rd, 2010.'
• Microsoft Visual Studio 2015: 'July 20, 2015: Visual Studio 2015 (“VS 2015”)'

Latest version December 6, 2019; Python 3.8 (October 14th, 2019), Visual Studio 2019 (April 2, 2019)............

[rvagg]

please stop reading old articles and assuming they indicate the current state of a piece of software, the date is even in the URL and it's 9 months old. see the node-gyp README for current state and if you have an old version, update it and try again, same with npm which can be updated with npm i npm -g and will bring in a newer version of node-gyp.

[Paulsky]

9 months ago is an old article in your opinion? Of course I followed the node-gyp README. Which did not fix my environment. Here is a more recent discussion (with a solution that worked for me); https://stackoverflow.com/a/57763427/4234891

[otoomey]

You do not need Python 2.7 in order to run node-gyp. Python 3 has been supported since version 5.0.5. If you have verified that your issue is python related, as in that node-gyp is trying to run a script which contains errors according to the python 3 interpreter, then try the following:

1. Update your global node-gyp install. npm install -g node-gyp
2. Update your npm install. npm install -g npm

Both modules are separate, npm will have its own copy of node-gyp. If you are trying to link a local package, for instance, npm will use its own copy of node-gyp. However, if you run node-gyp from the command line, it will use the other.

Of course, all of this is irrelevant if you don't have a valid installation setup. You will need build tools, as the previously linked articles mention. Windows voodoo dictates that you will probably have to mess around in order to get everything setup on the runtime side. However, you do not need python 2.7.

[HanqingTony]

Please look at this article from 2019: https://spin.atomicobject.com/2019/03/27/node-gyp-windows/

On Windows, you have to use Python 2.7 and Microsoft Visual Studio 2015:

• Python 2.7: 'Python 2.7.0 was released on July 3rd, 2010.'
• Microsoft Visual Studio 2015: 'July 20, 2015: Visual Studio 2015 (“VS 2015”)'

Latest version December 6, 2019; Python 3.8 (October 14th, 2019), Visual Studio 2019 (April 2, 2019)............

Previously I had started an Issue to suggested node-gyp should turn to python3. Couple of weeks ago, one of the contributor of node-gyp replied to me, saying that node-gyp now support pure python3. So I think there was no doubt that articles about python2 would be out of date

[parkertomatoes]

I ran into this on Win10. It was a pretty crummy experience. The Node v13 installer tried to install some node-gyp dependencies + Chocolatey, opened a command prompt which flashed an error message, then the window flashed away with no further error.

When I tried to npm install for an application, it broke when the node-gyp build for node-sass trying to find python2 and defaulted to python.exe which was Python 3.8, and broke on a print statement. I worked around it by installing Python 2.7, and creating a batch file called python2.bat with the following contents and adding its location to my PATH variable:

py -2 %*

BUT, because the Node installer failed to install all those dependencies for node-gyp, I also had to install VS build tool 2015 (v140) and 2017 (v141) and launch npm install from my VS build prompt to get it all to work correctly. I hope this silly workaround helps someone else though.

[cclauss]

Python 3.8 [...] broke on a print statement.

You are using a version of node or node-gyp that does not support Python 3. This was fixed a long time ago.

[richardlau]

Python 3.8 [...] broke on a print statement.

You are using a version of node or node-gyp that does not support Python 3. This was fixed a long time ago.

Looks like node-sass has a direct dependency on the outdated node-gyp 3.

https://github.com/sass/node-sass/blob/c6f2e5a1643dd00105b63a638756dc99fc33c3e4/package.json#L67

[parkertomatoes]

@cclauss You're right, it's an issue with a dependency and different than the one in the bug report. It's unfortunate that these errors appear as node-gyp errors. Thanks for the correction and thanks @richardlau for pointing out the potential issue with node-gyp. I'll file a bug report there.

[codler]

sass/node-sass#2801

[cclauss]

End of Life of Python 2 is TODAY. Can this issue be closed?