• Fix Current Password No Longer Matches Keyring Via Termiinal Iphone
• Fix Current Password No Longer Matches Keyring Via Termiinal App

I'm still working to get this figured out.

To that end, I've made a test keychain credential keyring_test, with user: foo and pass: bar.

I'm still getting error 25293 / errSecAuthFailed under Python 3.5.2, but I'm able to retrieve the test password under 2.7.12.

I've simplified the new ctypes OSX API to the following test script:

Interestingly, I found that I do get the popup to 'allow' and subsequently can access it under the following Python versions (with keyring 9.3.1):

Fix Current Password No Longer Matches Keyring Via Termiinal Iphone

1. python 2.7.12, installed by homebrew

2. python 2.7.9, installed by pyenv

3. either of the above python2, in a virtualenv

4. python 3.5.1, installed by homebrew (real path Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/bin/python3.5)

5. python 3.5.2, installed by pyenv

6. 3.5.2 from homebrew, in a virtualenv created by virtualenv

   I am not able to get it to work (get the error from above) in the following settings:

7. python 3.5.2, installed by homebrew (real path Cellar/python3/3.5.2/Frameworks/Python.framework/Versions/3.5/bin/python3.5)

8. python 3.5.2 from homebrew, in a virtualenv created by pyvenv using --symlinks

9. python 3.5.2 from homebrew, in a virtualenv created by pyvenv using --copies

Fix Current Password No Longer Matches Keyring Via Termiinal App

I am also driven mad by this “Enter password to unlock your login keyring” feature. I do know the password for that but don’t want to type it in every 5 minutes. But I’m none the wiser after reading all these different answers, several times!

This is really confusing at this point. Specifically,

• I'm surprised that #4 works whereas #7 doesn't (both homebrew installed, similar path with frameworks, the python3 formula doesn't seem to have crazy changes in the interim)
• I'm surprised that #6 works while #9 doesn't (at first I thought it was because pyvenv uses symlinks by default, but the --copies flag didn't make a difference)

It clearly doesn't seem to be a problem with Python, since 3.5.2 from pyenv works, as well as 3.5.2 from homebrew in a virtualenv installed virtualenv (but not a pyvenv installed virtualenv).

Any other ideas?