ember fails to install via npm on win7
Closed this issue · 1 comments
jcollum commented
$ npm install ember
gypgyp ERR!ERR! stackstack Error: Can't find Python executable "python", you can s et Error: Can't find Python executable "python", you can set the PYTHON env variable
I wonder if this is related?
npm WARN engine window@1.0.0: wanted: {"node":"0.6"} (current: {"node":"v0.8.16","np
m":"1.1.69"})
Here's more info:
npm http 200 https://registry.npmjs.org/bindings/-/bindings-1.0.0.tgz
> contextify@0.1.3 install c:\Users\jcollum\Dev\app\node_modules\ember\no
de_modules\window\node_modules\jsdom\node_modules\contextify
> node-gyp rebuild
> contextify@0.1.3 install c:\Users\jcollum\Dev\app\node_modules\ember\no
de_modules\jquery\node_modules\jsdom\node_modules\contextify
> node-gyp rebuild
c:\Users\jcollum\Dev\app\node_modules\ember\node_modules\window\node_modu
les\jsdom\node_modules\contextify>node "c:\Program Files\nodejs\node_modules\npm\bin
\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
c:\Users\jcollum\Dev\app\node_modules\ember\node_modules\jquery\node_modu
les\jsdom\node_modules\contextify>node "c:\Program Files\nodejs\node_modules\npm\bin
\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
gypgyp ERR!ERR! configure errorconfigure error
gypgyp ERR!ERR! stackstack Error: Can't find Python executable "python", you can s
et Error: Can't find Python executable "python", you can set the PYTHON env variable
ERR!PYTHON gypenv v ariable.
gyp stackERR! at failNoPython (c:\Program Files\nodejs\node_modules\npm\node_mo
dules\no de-gyp\lib\confstackigure at failNoPython (c:\Program Files\nodejs\node
nm.ojdsu:l1e1s2\:n1p4m)\
ode_modulegyps\nod e-gyp\lib\configERR!ure.js :112:14)stack
at c:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\lib\configure
.js:81:gyp11
gypERR! stackERR! at c:\Program Files\nodejs\node_modules\npm\node_modules\nod
ig gyp\libstack\conf at Object.oncomplete (fs.js:297:15) `
Are you relying on the end user to have Python in their PATH?
charlesjolley commented
hi - this is due to a dependency on jsdom from our dependency on jquery, which I believe tries to do a native build. Can you open this issues against jsdom?