-
Notifications
You must be signed in to change notification settings - Fork 317
Parentheses in path name breaks env.bat, stops Spyder.exe and other commands from running #375
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
Comments
Can you give an example of a path name with The "(" / ")" way of writing DOS was making it less of a pain to read.... shame |
so, something safety-belted like that:
the other places where " ) else (" is used are between doublequotes, so safe from the problem I suppose. |
When I was testing I used the folder c:/tmp/(tmp)/ to verify it wasn't path length. That second section of code you posted looks better, were you able to replicate the problem? The DOS was so ugly I couldn't get my head around it, offended my spoilt eyes that are so used to looking at Python ;) |
testing the fix, so it's in coming build. |
Uh oh!
There was an error while loading. Please reload this page.
Symptoms are that double clicking Spyder.exe just does nothing.
In WinPython-64bit-3.5.2.1Qt5 (and I believe other 3.4 and 3.5s) the test for R and Julia directories is done with the section
Which fails with the following error if there are any parentheses (specifically round brackets) in the path name;
\WinPython-64bit-3.5.2.1Qt5\scripts\..\python-3.5.2.amd64\..\tools\R was unexpected at this time.
In WinPython-64bit-2.7.9.5 this test was done with an 'if NOT exist' statement, which seemed to catch this error
I have tried copying the method into the 3.5.2.1 env.bat and have confirmed that it fixes the problem.
Although it's only a work around, because I'm guessing it doesn't solve the problem where the directory has parentheses in the name AND R or Julia exist.
Thanks to everyone who has put so much work into this great package.
The text was updated successfully, but these errors were encountered: