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

python 3.x breaks grunt serve #1914

Closed
craigryan opened this issue Aug 22, 2015 · 6 comments
Closed

python 3.x breaks grunt serve #1914

craigryan opened this issue Aug 22, 2015 · 6 comments

Comments

@craigryan
Copy link

Following the default jhipster setup, grunt serve fails with a python version error because of browser sync. I have python 3.x installed (Win 8.1).

Since jhipster indirectly depends on the python version installed I think it would be useful to mention in the installation doc to have python 2.x on PATH

@deepu105
Copy link
Member

Yes i noticed this too but i wasnt using browser sync so didnt know it was breaking stuff

@atomfrede
Copy link
Member

I have python 3.4.3 on PATH (Linux) and grunt serve works just fine.

@jdubois
Copy link
Member

jdubois commented Aug 23, 2015

I have Python 2.x installed (default install with Homebrew on Mac), and I don't have any issue. I'm not really aware on any issue, but if this is linked to Grunt or BrowserSync can you link to the issue on those projects? I would be very surprised that one of them as an issue with Python, but I haven't looked at them very deeply.

@craigryan
Copy link
Author

This only happens with a fresh project for me (no node_modules), after the
first build I guess python isn't called so any version can be installed.
The error I get (below) is fairly clear, browser sync build requires < 3.x
python which they'd probably point out if I logged an issue against it.
Up to you if you want to mention the indirect python 2.x dep in your docs,
for the sake of a better JH newbie experience.

The error:

...grunt-browser-sync\node_modules
browser-sync\node_modules\socket.io
\node_modules\socket.io-client\node_modules\e
ngine.io-client\node_modules\ws\node_modules\utf-8-validate>if not defined
npm_c
onfig_node_gyp
gyp ERR! stack Error: Python executable "python" is v3.4.3, which is not
support
ed by gyp.
gyp ERR! stack You can pass the --python switch to point to Python >=
v2.5.0 & <
3.0.0.
gyp ERR! stack at failPythonVersion
(D:\packages\nodejs\node_modules\npm\nod
e_modules\node-gyp\lib\configure.js:119:14)
...
gyp ERR! node -v v0.12.7
gyp ERR! node-gyp -v v2.0.1

On Mon, Aug 24, 2015 at 2:03 AM, Julien Dubois notifications@github.com
wrote:

I have Python 2.x installed (default install with Homebrew on Mac), and I
don't have any issue. I'm not really aware on any issue, but if this is
linked to Grunt or BrowserSync can you link to the issue on those projects?
I would be very surprised that one of them as an issue with Python, but I
haven't looked at them very deeply.


Reply to this email directly or view it on GitHub
#1914 (comment)
.

@gmarziou
Copy link
Contributor

Well known and very old gyp issue and as a consequence node-gyp does not support Python 3 either, even NodeJS requires gyp to build.

It's difficult to document it clearly and there's no simple solution if a user really needs Pyhton 3.x.
How many other issues depending on user's environment should we document if we start documenting this one? I'd be in favor of not documenting it.

@jdubois
Copy link
Member

jdubois commented Aug 25, 2015

If it's a node.js requirement we don't have to do anything: it's quite explicit that we rely on Node.js, and that it should be correctly installed.

@jdubois jdubois closed this as completed Aug 25, 2015
@jdubois jdubois modified the milestone: 2.20.0 Aug 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants