-
Notifications
You must be signed in to change notification settings - Fork 8
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
Installation docs update. #434
Comments
Also missing the example command: |
Thanks for sharing this @jamiesoon. Can you post the exact error message/traceback that you get? We can either post that in the docs, or just suggest that people search our github issues page to find any known/solved ones. And in future would you be able to open separate Github issues for separate problems? I can fix the second problem you noticed immediately in a PR. |
Unfortunately not as I didn't save the error message at the time. |
I'm not sure if that's true. At least, for the CI we pull up a clean ubuntu-2204:
and then install pip/poetry from scratch, without the PYTHON_KEYRING_BACKEND exporting. So perhaps it depends specifically on your platform version? In any case, I'm not sure we can do much more here. I will close for now, but if you (or anyone else) encounters it again please reopen and we can document for it! |
I've encountered this issue again when updating via poetry with the following error
Had to do "export PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring" again. |
When following the installation docs for installation an issue may arise when using poetry and access to a keyring.
This is a known poetry issue:
python-poetry/poetry#1917
and can be solved by using:
"export PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring"
None of the required packages should require the keyring so this should be added to the installation docs.
The text was updated successfully, but these errors were encountered: