You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My company would like to use it to avoid a chicken/egg problem (bootstrapping a single systemwide keyring binary with the appropriate keyring backend is easier than doing it for every installation of poetry), and to keep our configuration as in sync with pip as possible.
Workarounds
The alternative is for people to carefully configure their poetry venv to be configured the same as their global keyring installation.
The text was updated successfully, but these errors were encountered:
poetry is not pip and is not trying to imitate pip, I doubt it will ever add support for pip-specific environment variables
you could try rewording this in terms of a native poetry feature. But given that your workaround already is to configure poetry to do what you want it to do perhaps nothing is missing.
jfly
changed the title
Feature parity with pip's keyring support
Add support for keyring as a subprocess subprocess (rather than keyring as an import)
Jun 6, 2024
@dimbleby, got it. I've reworded this to just be a feature request asking for support for "keyring as a subprocess" in addition to poetry's "keyring as an import" functionality.
Issue Kind
Brand new capability
Description
Poetry has support for pulling authentication information out of the system keyring. This (largely) works the same as pip's keyring support, and the documentation even references pip's behavior:
However, poetry does not have support for invoking
keyring
as a subprocess (see pip's documentation for this here).Impact
The author of pip's keyring support actually intended for people to use it as a subprocess, rather than an import ("As the author of the
--keyring-provider
flag I recommend you use thesubprocess
provider").My company would like to use it to avoid a chicken/egg problem (bootstrapping a single systemwide
keyring
binary with the appropriate keyring backend is easier than doing it for every installation of poetry), and to keep our configuration as in sync with pip as possible.Workarounds
The alternative is for people to carefully configure their poetry venv to be configured the same as their global
keyring
installation.The text was updated successfully, but these errors were encountered: