Closed Boston-of-Gilead closed 1 year ago
Ok I've sort of fixed it.
Reinstalling Keyring - ineffective. Reinstalling Python - ineffective. Reinstalling VSCode - ineffective. Switching to PyCharm - ineffective.
I noticed WSL (Windows Subsystem for Linux) updated itself yesterday. I removed the update through appwiz - ineffective.
My work computer had bizarre networking issues from when I had WSL installed on it so I removed WSL - effective.
However my Keyring doesn't behave the same as the docs say.
keyring.get_password('TEST2','username')
Doesn't return anything.
However this now works (it wasn't before):
CRED = keyring.get_password('TEST2','username')
print(CRED)
Same for keyring.get_keyring()
and keyring.get_credential('TEST2','username')
which weren't working before either, but now will work as long as I set them to a variable after having WSL uninstalled, despite Python, Keyring, IDLE, and various IDEs all running on Windows.
I suppose going forward I'll have to keep my Docker/Linux activity on dedicated VMs rather than creating containers via WSL... and use variables for the Keyring contents.
Describe the bug Fresh install of Keyring not sending get_password to terminal. The credential appears in Credential Locker so set_password is working correctly.
To Reproduce My code:
The output:
Expected behavior
Environment
Additional context Add any other context about the problem here. Windows Credential Manager gets the entry: