We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the macOS Keyring backend hard-codes a few error codes to messages. Better would be to use the API to resolve error codes to human-readable message strings.
I started looking into how to do it. I imagine it goes something like:
>> api._sec.SecCopyErrorMessageString(-25244) -1797030505
But probably something needs to translate that integer response into a CFString object and convert that object to a Python string.
CFString
Maybe someone would be interested in determining how to do that?
The text was updated successfully, but these errors were encountered:
Hi @jaraco. Can you please assign me to this issue.
Sorry, something went wrong.
abastola0
No branches or pull requests
Currently, the macOS Keyring backend hard-codes a few error codes to messages. Better would be to use the API to resolve error codes to human-readable message strings.
I started looking into how to do it. I imagine it goes something like:
But probably something needs to translate that integer response into a
CFString
object and convert that object to a Python string.Maybe someone would be interested in determining how to do that?
The text was updated successfully, but these errors were encountered: