-
Notifications
You must be signed in to change notification settings - Fork 18
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
Explicitly depend on poetry-plugin-export #874
Comments
Note that this will become a more pressing issue because as of Poetry 1.7.0:
And perhaps soon: |
A potential Poetry feature that would really help solve this for |
Poetry 2.0 will have this and when it is released, we will need to update the docs here to instruct people on how to add the export plugin as a required plugin for their project |
What do we need to do to silence this warning and keep our projects running? |
For Poetry <2.0, this is documented here: https://python-poetry.org/docs/plugins#using-plugins Since it is another manual bootstrapping step, however, I'm personally allowing the warning to print until Poetry 2.0 is released and plugins can be explicitly declared as a dependency for a project, which scales much better with multiple team members. |
See
Since
nox-poetry
depends onpoetry-plugin-export
, it should document that users must install it or install it as a dependency (if that is supported for poetry plugins? A user might have to opt into this).The text was updated successfully, but these errors were encountered: