Python spaces in file path windows

The syntax for using raw string literals is shown below. For example, import os print os. Use the pathlib. See the code below. DelftStack is a collective effort contributed by software geeks like you. If you like the article and would like to contribute to DelftStack by writing paid articles, you can check the write for us page.

Active 5 years, 5 months ago. Viewed 6k times. Improve this question. Luca Luca 8, 14 14 gold badges 81 81 silver badges bronze badges. Possible duplicate of whitespaces in the path of windows filepath — shivsn. Possible duplicate of casting raw strings python — SiHa. Add a comment. Active Oldest Votes. Improve this answer. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. Note that both launcher scripts actually work when executed directly: only the launcher.

So it may be good to also make the launcher more forgiving is the bug tracker for distlib non-public? The text was updated successfully, but these errors were encountered:. Sorry, something went wrong. The error message is different. In this case, the pip seems to write a non-executable shebang line in contrast to python setup. Edit: Want to point out this was run under Windows I am having the same problem, only it manifests itself because the user name has a space in it.

The issue here appears to be the same as one I've experienced with pip 1. It is not a Windows bug per se. The "shebang" line hash-bang, or! The workaround might be to create a symlink which doesn't have a space in the path. Sadly, the issue is not trivially remediable by mere quoting. Edit: as Janzert indicates below, the problem I reproduce appears not to be related to the Windows problem of the instant issue.

Same symptom with different causes -- leaving this comment above intact to help future readers disambiguate where to be spending time. Remember Windows itself doesn't do anything with shebang lines. So it is handled by the launcher executable from distlib directly.

A quick skim of the launcher source seems to show that it does explicitly and correctly handle double quotes around the interpreter command. I encountered the same problem in my pandoc-eqnos project.

See Issue 6. It occurs on Windows 10 installations, but not 7. I haven't tested 8.