-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Broken path parsing for install spec #6032
Comments
Thanks! cc @charliermarsh might a regression from #5888 |
I can take a look. |
Ah, sorry, I should have said that there is also an error with older versions before that PR (e.g. 0.2.32) The underlying issue of something splitting the path at the space is older. |
I think we currently require that you use a backslash here. |
(But of course it should work as-is.) |
I wasn’t aware that escape sequences in dependency specs are a thing at all! |
Yeah it's a bit tricky. Like this doesn't work:
But it does work if you quote it, or pass it directly on the command-line etc. |
I am quoting it, see initial comment. |
Yeah I'm describing what the behavior should be, not what we do today. |
I see! Thank you for clarifying! |
The text was updated successfully, but these errors were encountered: