Skip to content
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

Open
johnthagen opened this issue Sep 1, 2022 · 5 comments
Open

Explicitly depend on poetry-plugin-export #874

johnthagen opened this issue Sep 1, 2022 · 5 comments

Comments

@johnthagen
Copy link

See

To reflect this, and to accelerate development of the main Poetry project, it has been migrated into a separate repo and is distributed separately as poetry-plugin-export.

To ease the transition, the plugin is installed by default for the 1.2 release. Future releases of Poetry will deprecate this automatic install, and require the user to explicitly install the plugin.

Since nox-poetry depends on poetry-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).

@johnthagen
Copy link
Author

johnthagen commented Nov 7, 2023

Note that this will become a more pressing issue because as of Poetry 1.7.0:

Print a future warning that poetry-plugin-export will not be installed by default anymore

And perhaps soon:

@johnthagen
Copy link
Author

A potential Poetry feature that would really help solve this for nox-poetry users is:

@johnthagen
Copy link
Author

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

@bosd
Copy link

bosd commented Oct 15, 2024

What do we need to do to silence this warning and keep our projects running?

@johnthagen
Copy link
Author

johnthagen commented Oct 15, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants