Cannot install plugins within poetry about homebrew-core

[woodruffw]

Unfortunately I suspect this won't work, at least not with any poetry plugin that wants to upgrade Homebrew's Python environment: allowing these kinds of resolution changes would allow anything that gets brew installed to break other Homebrew-managed Python applications.

I believe there are two resolutions possible here:

• We could package this poetry plugin as a formula with the same Python dependency as poetry itself, which would drop it into the same environment. Then, you could do brew install poetry-dynamic-version to enable it.
• You could put poetry into its own environment, which is (probably) how it wants to be used (I don't know poetry super well, but this is what their docs suggest). I think brew install pipx; pipx install poetry; pipx inject poetry "poetry-dynamic-versioning[plugin]" would suffice for that.

[twam]

I personally would prefer a way, that is managed by brew, so that a brew upgrade will also update poetry and its plugins.

The second suggestion works for now, but feels wrong, as there is a poetry package provided by brew which I cannot use. :)

[SMillerDev]

You can make your own tap and maintain a package there.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[btonasse]

Encountering the same issue :(

[woodruffw]

Encountering the same issue :(

Have you tried either of the resolutions suggested above? Relying with a "me too" comment on its own doesn't help us address the underlying problem.

Keep in mind: Homebrew does not distribute Python with the expectation that arbitrary third-party packages can be loaded into Homebrewed Python's environment. If this is a capability that you need, you must use pip, pipx, or pyenv, depending on the layer of abstraction you need. For poetry, pipx with dependency injection is probably the simplest option, and seems to be recommended by poetry's maintainers.

[btonasse]

I do not expect you to "solve it", but I think developers like to have an idea of how many users are encountering an issue and how problematic it is for them. That alone is worth a "me too" post. You're of course free to do whatever you want with that information. But last time I checked this issue was not closed.

And yes, refraining from installing poetry with homebrew sidesteps the problem.

[heidi-jack]

I was also experiencing this issue, in the end I just uninstalled poetry via brew and installed it outside of brew. Not worth the faff. Not a solution within brew unfortunately but it unblocked me from getting work done

https://python-poetry.org/docs/#installing-with-the-official-installer

[woodruffw]

I think this is currently non-actionable on Homebrew's side. Our recommendations to users who need Poetry plugins are:

1. brew install pipx && pipx install poetry and use pipx's environment injection abilities to load plugins into Poetry's virtual environment (described above)
2. Do python -m venv env && env/bin/python -m pip install poetry if using a directly managed virtual environment is appropriate for your use case
3. brew install pyenv and then pyenv to install a non-Homebrew version of Python without PEP 668 restrictions, and then pip install --user poetry directly (if that's what you want)
4. Use Poetry's own installer (keeping in mind that Homebrew doesn't check the contents of this installer, and doesn't guarantee that it works correctly with the Homebrewed Python)