Closed mairsbw closed 8 years ago
I don't use Windows! So...no, I really have no idea.
@MinchinWeb @jayvdb Do you guys have any ideas on this?
I can confirm the issue. I tried running green --version
on a fresh system going back to green
1.8 and the issue ('failed to create process`) came up each time. My guess is there is some dependency that is not being installed...
I suspect it may be this issue with using pip to install --> https://github.com/pypa/pip/issues/2783
The issue is that the green launcher is being install into a directory with a space in the path. To workaround, I would suggest you download the code, and then install manually using python setup.py install
. Let me know if that works.
Maybe this is the underlying problem, and is now fixed?
https://github.com/pypa/setuptools/issues/398#issuecomment-225444249
Unless someone knows otherwise, I will consider this as a bug in setuptools on Windows that has been fixed in some recent setuptools release.
@mairsbw , @MinchinWeb , can you check whether you have installed python in a directory with spaces in the name? I will have access to a decent Windows maxhine tomorrow.
But we should be able to reproduce this on Appveyor.
@jayvdb The default installation directory for Python 3.5 on Windows is now the Program Files directory, so my Python 3.5 is installed to C:\Program Files\Python 3.5\python.EXE
.
My green wasn't working, so I uninstalled it with pip and then reinstalled it (just now), and green seems to be working now. So hopefully this is now fixed in setuptools, and remains that waypip . I'm currently running Windows 10x64, Python 3.5.2, pip 8.1.2, setuptools 24.0.3, and green 2.5.1.
This is probably the same problem as https://github.com/CleanCut/green/issues/98
@jayvdb The way I described it, this may well be the same as 98. Good catch.
I installed
green
using pip with administrator permissions on my Windows 10 x64 machine where Python3.5 is install into Program Files. After installing if I rungreen green.examples
I see onlyfailed to create process
and the program returns. But if I run it likepython -m green green.examples
, then it works correctly. It looks like that program is an executable, so it shouldn't be a Python pathing issue. Any ideas what's going on here?