-
-
Notifications
You must be signed in to change notification settings - Fork 157
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
Importing keyring fails (because of secretstorage requirement) #338
Comments
Diving into this a bit more, it could be because recently (version 3.0 released in april) secretstorage switched to jeepney (mitya57/secretstorage@711c931) which is raising a different exception (the So if I |
Please try the latest version of SecretStorage from master branch, it should handle such errors properly. |
@mitya57 - Thanks a lot, it should indeed do the job, I will check tomorrow. |
It works, thanks again @mitya57 ! |
I have just released SecretStorage 3.1.0, which now catches such errors and converts them into its own exceptions (which would be caught by python-keyring). |
I'm having some trouble with keyring on a server, on which I don't want to configure / use Dbus (I could try to setup dbus, but I don't want to explain this to every user of my code).
Currently keyring is imported on a dependency of my project, and it has secretstorage as dependency, which means that I cannot even import keyring:
It makes it impossible to list backends, or to view the config path, or even to change the backend! (even if I set
keyrings.alt.file.PlaintextKeyring
in the config file).I can uninstall secretstorage, then keyring work and can use
keyrings.alt
, but then when I run a script usingentry_points
, pip checks the requirements and fails because secretstorage is missing :(The text was updated successfully, but these errors were encountered: