Initializing poetry exits in SecretStorage required, regardless of SecretStorage already installed

[anoduck]

Decided to start discussion rather than submit a bug, because unsure the error received is related to a bug. Just trying to figure out what is going on with poetry in my instance.

Every time I attempt to initialize a new project with poetry, it ends with the output SecretStorage required. This is regardless of having the SecretStorage module installed or not.

Enter the version constraint to require (or leave blank to use the latest version): 

SecretStorage required

Cache for poetry and pip have both been purged. Currently, SecretStorage has been installed through the system package management system.

[anoduck]

Error resolved when #1917 was gratefully pointed out to me.

It wasn't necessarily "SecretStorage" causing the received error, it was that "python-keychain" was looking for "SecretStorage" to be configured and implemented, when it was not. A few weeks ago, I attempted to implement "secretservice" for another application, but abandoned the implementation. I knew there was a modified configuration file somewhere on my system that was configured to use the now defunct "secretservice" implementation, but since I never received any sign specifically pointing to this misconfigured file, I assumed it wasn't a concern. When all along, poetry was pointing right at the issue, in it's own way.

~/.config/python-keyring/keyringer.cfg was the file in question that was modified to use the defunct "secretservice" implementation. I simply exchanged default-keyring=keyring.backends.secretservice.Keyring for default-keyring=keyring.backends.null.Keyring. Immediately after which, poetry ceased output of the error, and is back to working fantastically.

[anoduck]

You can now applaud my absent-minded greatness... ROFL...