-
Notifications
You must be signed in to change notification settings - Fork 15
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
Build fails on requirements.txt schema not followed correctly #206
Comments
Workarounddowngrade poetry self add poetry-plugin-export@1.7.1 |
the issue can be also resolved by setting the [tool.poetry.dependencies.mylib]
path = "../../../libs/mylib"
- develop = true
+ develop = false |
@kenyerman thanks for reporting this issue, well, the problem with the I'll work on this |
In the poetry-plugin-export@1.8.0 the requirements.txt format has changed for local dependencies from `<packageName> @ file://<location>` to `-e file:///` re #206
In the poetry-plugin-export@1.8.0 the requirements.txt format has changed for local dependencies from `<packageName> @ file://<location>` to `-e file:///` re #206
#207 solves this issue, confirmed. Thanks for the very quick support! 🎉🎉🎉 |
Current Behavior
Since python-poetry/poetry-plugin-export#258 was merged, the temporary
requirements.txt
format's changed. This makes local project dependencies unparseable, making the build fail.Relevant snippets
tailored output
requirements.txt with poetry-plugin-export@1.7.1
requirements.txt with poetry-plugin-export@1.8.0
Expected Behavior
build succeeds
Steps to Reproduce
1. install latest poetry-export-plugin
2. watch the build fail
Nx Report
Failure Logs
No response
Additional Information
The error is in:
packages/nx-python/src/executors/build/resolvers/locked.ts:67
strategy of parsing local dependencies from
requirements.txt
must be rewritten.The text was updated successfully, but these errors were encountered: