-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Poetry 1.1.2 uses an invalid format when exporting local file dependencies #3189
Comments
Hi. I'm having a very similar issue. According to this PEP 440, the format is right, but when running the command of pip install, it can't find the path correctly. Maybe is missing the |
@eduardofb That seems to be the issue, manually adding |
The problem still appears in version |
This change ensures that when exporting `requirements.txt`, local direct reference dependencies are exported as uri and not paths. Resolves: #3189
This change ensures that when exporting `requirements.txt`, local direct reference dependencies are exported as uri and not paths. Resolves: python-poetry#3189
This change ensures that when exporting `requirements.txt`, local direct reference dependencies are exported as uri and not paths. Resolves: #3189
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option).Issue
While I see a bunch of new issues for export, I don't see anything specifically for this one, and want to make sure it doesn't get missed.
poetry export
for poetry 1.1.2 uses an invalid/deprecated format for local file dependencies, however poetry 1.0.10 does not.Specifically, it uses the
package @ path/to/local/file.whl
format, which does not work for pip 20.0.1 or later. Notably, the format did not cause an error when 19.2.3 was installed.I noticed this bug after updating poetry from 1.0.10 to 1.1.2. Our build process builds a Docker image that pip installs the exported requirements file.
Steps to reproduce:
Copy-paste-friendly version of steps (no $ or output)
Actual behavior/output (1.1.0 and 1.1.2)
Expected behavior/output (1.0.10)
PEP 400 expected output
The text was updated successfully, but these errors were encountered: