Can't find Python executable "python" after installing #56

mikew · 2017-04-23T08:09:58Z

node-gyp is failing because it can't find python. windows-build-tools did its thing and python is installed:

$ $(npm config get python)
Python 2.7.11 (v2.7.11:6d1b6a68f775, Dec  5 2015, 20:32:19) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> exit()
$ npm --version
4.5.0
$ node --version
v7.9.0

Here's the output from node-gyp:

+ node_modules/.bin/electron-rebuild --arch x64 -f -p -w serialport -m electron-app
× Rebuild Failed
An unhandled error occurred inside electron-rebuild
gyp info it worked if it ends with ok
gyp info using node-gyp@3.6.0
gyp info using node@7.9.0 | win32 | x64
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (C:\Users\mike\Work\dronefuse-client\node_modules\node-gyp\lib\configure.js:482:19)
gyp ERR! stack     at PythonFinder.<anonymous> (C:\Users\mike\Work\dronefuse-client\node_modules\node-gyp\lib\configure.js:508:16)
gyp ERR! stack     at C:\Users\mike\Work\dronefuse-client\node_modules\graceful-fs\polyfills.js:284:29
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:114:15)
gyp ERR! System Windows_NT 10.0.15063
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\mike\\Work\\dronefuse-client\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--target=1.4.13" "--arch=x64" "--dist-url=https://atom.io/download/electron" "--build-from-source" "--module_name=serialport" "--module_path=C:\\Users\\mike\\Work\\dronefuse-client\\electron-app\\node_modules\\serialport\\build\\Release" "--host=https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7"
gyp ERR! cwd C:\Users\mike\Work\dronefuse-client\electron-app\node_modules\serialport
gyp ERR! node -v v7.9.0
gyp ERR! node-gyp -v v3.6.0
gyp ERR! not ok

The text was updated successfully, but these errors were encountered:

mikew · 2017-04-23T08:33:21Z

It's as if npm isn't even checking the value of python that is set, because this invocation works:

PATH="$(dirname $(npm config get python)):$PATH" node_modules/.bin/electron-rebuild --arch x64 -f -p -w serialport -m electron-app

tkgalk · 2017-05-12T09:06:41Z

Same issue here.

choucry13 · 2017-05-17T13:04:20Z

+1

garolion · 2017-05-26T22:54:12Z

solution: nfroidure/ttf2woff2#28
npm install --global --production windows-build-tools

felixrieseberg · 2017-06-08T01:42:53Z

Hm, seems like this is more with electron-rebuild than with npm. I assume the real solution here is to also ensure that python is globally accessible, which would require checking if it isn't already.

I'd gladly accept a PR for that, I'm not sure when I'll get to it.

ArminMa · 2017-06-15T14:00:33Z

https://github.com/felixrieseberg/windows-build-tools/issues/33

npm --add-python-to-path='true' --debug install --global windows-build-tools

jeanru · 2017-09-06T08:52:57Z

npm config set python "c:\Python\27\python.exe"

dougbacelar · 2017-10-19T14:27:50Z

@ArminMa solution solved my issue! Had to run the CLI as administrator.

harrodevos · 2017-11-17T11:10:23Z

@ArminMa's solution worked for me too!

I first had Python version 3.6 for Windows installed on a Windows Server 2016 machine. I used the windows executable installation.

This was required in order to install the web3 package.

But no matter how I set path and environment variables, during the npm install of web3 it kept complaining it couldn't find the python executable. Typing python in the command prompt worked fine.

I suspect it has to do with version/compatibility issues between web3 and python. After uninstalling the 3.6 version of python and installing 2.7 using the npm command ArminMa suggested it all works!

I did update my environment variables (PYTHON and PATH) to the 2.7 executable.

thuyvtgl · 2017-12-06T15:32:51Z

Thank guys,
especially thank @ArminMa, you solved my issue.

dhanabalcbt · 2017-12-30T12:22:21Z

thanks arima

Philip-Nunoo · 2018-01-19T09:52:57Z

Thanks @ArminMa

mapplics · 2018-01-26T09:44:23Z

thanks @aminma you save my day!

bibhuticoder · 2018-01-31T08:43:05Z

Installing python 2.* worked for me.

hallss93 · 2018-02-08T14:30:29Z

@garolion obrigado. Estive com esse problema por um bom tempo. Consegui corrigir com isso! 🥇

SatishMHiremath · 2018-02-17T17:46:55Z

I have faced and fixed this issue relates node-sass and python error.Try installing latest angular cli command with the steps below

Set the system variable path as well:
C:\Users\windowsusername\AppData\Roaming\npm

C:\Users\windowsusername\AppData\Roaming\npm\node_modules@angular\cli\bin;

C:\Program Files\nodejs;

Then start using angular cli command prompt using:
angular client project folder path>npm install -g @angular/cli@latest

angular client project folder path>npm install -g node-gyp

walalm · 2018-06-05T16:18:28Z

Executing: npm install --global --production windows-build-tools and then
executing npm rebuild did the trick.

hadnazzar · 2018-06-07T10:52:41Z

On windows:
Run powershell as Administrator:
and run
npm --add-python-to-path='true' --debug install --global windows-build-tools

lukos · 2019-06-12T13:17:06Z

The problem is more fundamental than is mentioned here. A node module should not have a hard dependency on a build system like Python or MSBuild unless it can download one and install it without privileges locally or hold the user's hand.

This package is a help but it doesn't solve the problem because if, for example, you need to install it from an admin account, it gets installed in the admin account which makes it unusable for the non-admin users.

I had to delete where it was installed and then manually install the Python executable for all users, but the modify path didn't seem to do anything because it still didn't work. I then manually added the PYTHON environment variable before it would work.

Thanks for this package but it should either have some more instructions, a better default example in the docs (and shouldn't be needed if people didn't make ridiculous node package like node_gyp)!

rashmimilan · 2019-09-20T11:14:47Z

https://github.com/felixrieseberg/windows-build-tools/issues/33

npm --add-python-to-path='true' --debug install --global windows-build-tools

Thank you so much @ArminMa!

ghost · 2019-10-02T09:24:12Z

Special thanks goes to @ArminMa ! works for me!

zaid757 · 2019-11-22T14:41:09Z

1 - Just uninstall Python from "C:\Users\username.windows-build-tools\python27"
2 - Reinstall running the msi install file, not command line. Link: https://www.python.org/downloads/release/python-2715/
2.1 - Check the option "Install for all users" and install on "C:\python27".

Now node-gyp will find the Python normally

it works halfway for me after I install python I need to install visual studio_BuildTools manually and select few other package too . now its working fine

tayyabarif41 · 2019-11-23T09:48:37Z

solution: nfroidure/ttf2woff2#28
npm install --global --production windows-build-tools

it worked <3

brianli-whitbread · 2019-12-11T14:08:35Z

npm config set python "c:\Python\27\python.exe"

@jeanru, this command destroyed my development machine.

To fix this, remove npm env variables from ~/.npmrc

tijazz · 2019-12-30T01:39:52Z

If you ever come across the above error on windows:
Run CMD as Administrator:
and run.
npm --add-python-to-path='true' --debug install --global windows-build-tools

that's all...

B4Lee · 2020-01-07T16:24:48Z

I just solved the problem by reading this article

https://spin.atomicobject.com/2019/03/27/node-gyp-windows/

hope it helps !!

ashutoshsoni · 2020-01-13T19:50:34Z

Thanks Satish.

divya-kanak · 2020-01-18T05:35:20Z

Configuration: window 10, 64 bit, node v8.13.0, npm v6.4.1

Follow the below steps :

Restart the system
Open cmd by administrator
Delete C:\Users\user_name.node-gyp
Delete %AppData%/npm
Delete %AppData%/npm-cache
Check out node-gyp package
npm install -g node-gyp
npm install --global --production windows-build-tools
node-gyp configure --python C:\Users\pcq158.windows-build-tools\python27\python.exe
npm config set msvs_version 2017 --global
npm install

krychuq1 · 2020-01-21T11:49:02Z

I had to re-install python 2.7 and change npm python config to:

npm config set python "c:\Python27\python.exe"

jawad-aziz-farhad · 2020-03-03T15:43:11Z

For Ubuntu 18.04.4 LTS
npm --add-python-to-path='true' --debug install --global build-tools

felloz · 2020-09-15T18:30:21Z

When i run npm --add-python-to-path='true' --debug install --global windows-build-tools

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! windows-build-tools@5.2.2 postinstall: `node ./dist/index.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the windows-build-tools@5.2.2 postinstall 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\lserrano\AppData\Roaming\npm-cache\_logs\2020-09-15T18_29_25_510Z-debug.log

Still having the issue

iwasherefirst2 · 2020-12-04T14:03:06Z

Its not working on Ubuntu:

npm --add-python-to-path='true' --debug install --global windows-build-tools
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for windows-build-tools@5.2.2: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! notsup Valid OS:    win32
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   linux
npm ERR! notsup Actual Arch: x64

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/adam/.npm/_logs/2020-12-04T14_01_39_361Z-debug.log

Any ideas how to fix it on Linux?

jacobq · 2020-12-04T14:08:31Z

This module literally downloads and installs some Windows binaries (e.g. MS Build Tools). It will not work on Linux (and is not needed in that case). That is what this error message is trying to convey.

…

On Fri, Dec 4, 2020, 8:03 AM Adam Nielsen ***@***.***> wrote: Its not working on Ubuntu: npm --add-python-to-path='true' --debug install --global windows-build-tools npm ERR! code EBADPLATFORM npm ERR! notsup Unsupported platform for ***@***.***: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"}) npm ERR! notsup Valid OS: win32 npm ERR! notsup Valid Arch: any npm ERR! notsup Actual OS: linux npm ERR! notsup Actual Arch: x64 npm ERR! A complete log of this run can be found in: npm ERR! /home/adam/.npm/_logs/2020-12-04T14_01_39_361Z-debug.log Any ideas how to fix it on Linux? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#56 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMOZMYMNZHVUAGWOWP6I73STDT2XANCNFSM4DIVLJNQ> .

iwasherefirst2 · 2020-12-04T14:23:49Z

@jacobq whoups. Just realized that I was actually missing Python at all.lol..

alvaropsouza · 2021-01-07T13:13:11Z

https://github.com/felixrieseberg/windows-build-tools/issues/33

npm --add-python-to-path='true' --debug install --global windows-build-tools

i think i love you. it worked man, thanks a lot!

SergeyAP · 2021-01-18T12:24:34Z

Its not working on Ubuntu:

npm --add-python-to-path='true' --debug install --global windows-build-tools
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for windows-build-tools@5.2.2: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! notsup Valid OS:    win32
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   linux
npm ERR! notsup Actual Arch: x64

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/adam/.npm/_logs/2020-12-04T14_01_39_361Z-debug.log

Any ideas how to fix it on Linux?

How did you fix it? i have the same problem on macos

jacobq · 2021-01-18T14:21:41Z

Its not working on Ubuntu: ...

How did you fix it? i have the same problem on macos

As the name windows-build-tools is intended to suggest, this package is for installing Windows software needed to build native extensions/modules for NodeJS. It is completely unnecessary on Linux and MacOS. If you are intending to "cross-compile" Windows things on a non-Windows platform then I recommend using a virtualization layer (e.g. VirtualBox, Parallels, etc.) or cloud CI/CD offering (e.g. AppVeyor).

sotickmars · 2021-02-17T08:31:23Z

run: npm cache clean --force
delete node_modules
delete packagelock.json and yarn.lock(if have)
run: npm install

danieldanielecki · 2021-03-25T10:52:07Z

Installing Python from the official source fixed this issue on Windows after restarting the machine...

reuniware · 2021-05-27T15:17:08Z

solution: nfroidure/ttf2woff2#28
npm install --global --production windows-build-tools

Thanks !!

OxQ · 2021-05-31T14:13:20Z

Installing python (for Windows) using Microsoft Store has helped me.

fabiovaz · 2021-07-02T19:14:56Z

after install windows build tools type
npm config set msvs_version 2017
saved me

hemano mentioned this issue Oct 12, 2017

error appium/appium#9183

Closed

kylebarron mentioned this issue Nov 28, 2017

Windows support kylebarron/stata-exec#4

Closed

matheusd mentioned this issue Jan 9, 2018

Update electron to 1.7.10 decred/decrediton#1064

Merged

This was referenced Feb 5, 2018

How to install Anaconda3 on Windows leo-editor/leo-editor#699

Closed

How to install zerorpc on Windows leo-editor/leo-editor#701

Closed

This was referenced Feb 20, 2018

Installation issue on windows web3/web3.js#1273

Closed

Web3 Installation Error web3/web3.js#1106

Closed

DanielMeltesen-zz mentioned this issue Feb 27, 2018

Node-gyp Error DGI-IT-zz/DGI_frontend_assignment#1

Open

gfmoore mentioned this issue Mar 4, 2018

Windows works!!! jkeylu/node-mpg123-util#5

Open

alex-page mentioned this issue Apr 16, 2018

Build issues on Windows environments govau/design-system-starter#12

Closed

ghost mentioned this issue May 28, 2018

Unable to install Firebase on new project firebase/firebase-js-sdk#873

Closed

nivida mentioned this issue Jul 17, 2018

npm install web3 failed web3/web3.js#1776

Closed

mrn06ody mentioned this issue Aug 21, 2019

Cannot build the project SimulatedGREG/electron-vue#917

Closed

zabil mentioned this issue Oct 24, 2019

unable to install taiko-screen cast on windows 10 getgauge-contrib/taiko-screencast#8

Closed

garretthyder mentioned this issue Sep 21, 2020

npm install on windows 7 python2 not found error and node-sass@3.13.1 error JeremyEnglert/JointsWP#317

Closed

jacobq mentioned this issue Jan 20, 2021

Cannot install windows-build-tools (Ubuntu for Windows) #235

Closed

RSamaium mentioned this issue Sep 30, 2021

Getting a build failed when doing npm i RSamaium/RPG-JS#106

Closed

eliodemollari mentioned this issue Dec 20, 2021

Renew local environment Setup taia-x/taia-x#105

Closed

Can't find Python executable "python" after installing #56

Can't find Python executable "python" after installing #56

Comments

mikew commented Apr 23, 2017

mikew commented Apr 23, 2017

tkgalk commented May 12, 2017

choucry13 commented May 17, 2017

garolion commented May 26, 2017

felixrieseberg commented Jun 8, 2017

ArminMa commented Jun 15, 2017

jeanru commented Sep 6, 2017

dougbacelar commented Oct 19, 2017

harrodevos commented Nov 17, 2017

thuyvtgl commented Dec 6, 2017

dhanabalcbt commented Dec 30, 2017

Philip-Nunoo commented Jan 19, 2018

mapplics commented Jan 26, 2018

bibhuticoder commented Jan 31, 2018

hallss93 commented Feb 8, 2018

SatishMHiremath commented Feb 17, 2018

walalm commented Jun 5, 2018

hadnazzar commented Jun 7, 2018 • edited Loading

lukos commented Jun 12, 2019

rashmimilan commented Sep 20, 2019 • edited Loading

ghost commented Oct 2, 2019

zaid757 commented Nov 22, 2019

tayyabarif41 commented Nov 23, 2019

brianli-whitbread commented Dec 11, 2019 • edited Loading

tijazz commented Dec 30, 2019

B4Lee commented Jan 7, 2020

ashutoshsoni commented Jan 13, 2020

divya-kanak commented Jan 18, 2020

krychuq1 commented Jan 21, 2020

jawad-aziz-farhad commented Mar 3, 2020

felloz commented Sep 15, 2020

iwasherefirst2 commented Dec 4, 2020

jacobq commented Dec 4, 2020 via email

iwasherefirst2 commented Dec 4, 2020

alvaropsouza commented Jan 7, 2021

SergeyAP commented Jan 18, 2021

jacobq commented Jan 18, 2021 • edited Loading

sotickmars commented Feb 17, 2021

danieldanielecki commented Mar 25, 2021 • edited Loading

reuniware commented May 27, 2021

OxQ commented May 31, 2021

fabiovaz commented Jul 2, 2021

hadnazzar commented Jun 7, 2018 •

edited

Loading

rashmimilan commented Sep 20, 2019 •

edited

Loading

brianli-whitbread commented Dec 11, 2019 •

edited

Loading

jacobq commented Jan 18, 2021 •

edited

Loading

danieldanielecki commented Mar 25, 2021 •

edited

Loading