-
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
keyrings.alt.Windows used unter linux if python 3 used #1968
Comments
There is the similar problem in This issue may be resolved with the upgrade of |
Yes, it helps to remove |
Similar error on linux where an OSX keyring plugin raises an error:
Looks like it could be useful to build some plugin abstractions for OS-specific init that handle any module-missing exceptions gracefully. |
This will not work since you basically are asking poetry to execute under an environment that it was not installed into. I'd suggest trying a new version of poetry installed using a method mentioned at https://python-poetry.org/docs/#installation. This is also likely issues with keyring not functioning correctly under a non-interactive environment. There are improvements to that part of the code in upcoming releases. #8623 #9065 Meanwhile if keyring issues persist use temporarily. export PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring If the issue is different to existing ones, please file a new issue with information on how best we could reliably reproduce it. |
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
I like to start poerty directly with Python v3, so i change the shebang in ~/.poetry/bin/poetry to:
#!/usr/bin/env python3
But then i get a very strange traceback while
poetry publish
:The text was updated successfully, but these errors were encountered: