-
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
Export command produces requirements.txt with git dev dependency #875
Comments
Also:
We would like to use the export function for production builds, using Serverless Framework. Any such feature on the horizon? |
TODO has been added for fixing this. |
The argument should be Using |
Just ran into this using |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
[An activity against robot auto-closing (which won't solve the issue at all)] |
I'd like to add extra debugging info to this issue. Using
|
The problem seems to be that the Git dependency belongs to category |
In fact, it's not the locker, but when the I'd be happy to create a PR to fix this issue. |
I've created a PR that fixes this issue. |
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
First off, poetry is awesome. Thank you for a great step forward in Python dependency management.
Using the above pyproject.toml, I run
poetry export -f requirements.txt
, and it produces thisrequirements.txt
webassets
is included in the requirements.txt without adding the--dev
to theexport
command.The text was updated successfully, but these errors were encountered: