-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Parse error for file on Linux #2323
Comments
Yes. If the file exists then it's fine. Should have a better error message at least. |
Contributions are welcomed! |
|
@techalchemy Sorry, If local files are not allowed, then the bug is that they work on Windows. |
Well if that works let’s keep it that way. No harm being lenient :) Let’s focus on providing better error messages. |
@OrangeDog they are allowed. They are not allowed in a |
@techalchemy that's why I said local files, not local paths. |
I have no clue why what you call it matters. A relative path goes in a path entry. Local files are completely fine and they work just fine in file keys, but you need to format them as a file uri. It’s possible you are crossing pipenv versions but this library works the same on all platforms in the current release and should fail to parse invalid requirements no matter what. |
@techalchemy we seem to be talking at cross purposes. I'm calling a path a path and a file a file. Apparently one goes in
That's not what I'm seeing (current release is 2018.05.18), because on Windows a |
hmmm I see. We must be doing some kind of odd normalization. I'll dig into this before we release |
Confirmed that this problem still exists:
|
If I'm reading this correctly, I'm not sure what the right approach to fixing this would be. |
Hi, I've tested the command Test environment
Output`root@623cff45dafb:/opt/test# pipenv install --skip-lock --dev ✔ Successfully created virtual environment! |
This is almost the same as #2256 except the workaround (use forward slashes) doesn't work.
Pipenv 2018.05.18
This dependency works great on Windows
However, running
pipenv install --skiplock --dev
on Linux (the Docker image python:3.6 to be exact) gives this error:Is it because the file doesn't exist? I would expect it to not care because the marker doesn't match.
The text was updated successfully, but these errors were encountered: