Python version 3.12rc1 - cannot find backend (Windows 11) and fatal exception in set
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with the shown Python 3.12-rc1 Windows command and the trivial test_keyring.py program, using -X faulthandler to reproduce the access violation. Compare keyring list-backends and the set_password/get_password calls with the reported Python 3.8.10 behavior; done means the backend is found and the sample completes without an interpreter crash.
Written by the indexing model from the issue text.
Description
- keyring list-backends gives nothing when installed on a Python 3.12-rc1 virtual environment.
- calling get_password cause an exit from the Python interpreter
they work perfectly under Python 3.8.10 with previous and the latest versions of keyring
o/s is Microsoft Window 11 pro (10.0.22621) and I am NOT working in a VM or Linux just a command shell
I am not running with admin privs
having just hound the Python -X faulthandler option I get this when running a trivial set and get program, the fault happening in the set call.
(z312) C:\Users\****************\Python\z312>py -X faulthandler ..\zzzz\test_keyring.py
Starting....
Windows fatal exception: access violation
Current thread 0x000055c4 (most recent call first):
Windows fatal exception: access violation
The trivial code is
import keyring
print( 'Starting....' , flush=True )
keyring.set_password("mySystem", "myUsername", "S3CR3T_P455W0RD")
print( 'password should be set' , flush=True )
saved_password = keyring.get_password("system", "myUsername")
print( f'{saved_password=} which I believe is a generic password set above ' )
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 208
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from jaraco/keyring
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
macOS: denied keychain prompt on delete raises PasswordDeleteError instead of KeyringLockedPossibly taken @r3wretrhy claimed this 46 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Remove B018 suppressions after adopting skeleton's B018 ignorePossibly taken @Madin-H23 claimed this 26 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 78/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/kernels#1006 ·
Maintainers usually reply within 1 day
-
precond_kda (new op, #1552) backward kernels hit CUDA illegal memory access on Blackwell under triton 3.3.1, pass under triton 3.7.1Possibly taken @YYuJLiu claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fla-org/flash-linear-attention#1749 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bridgecrewio/checkov#7804 ·
Maintainers usually reply within 2 days
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
triage/confirmed
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
agentscope-ai/agentscope#4068 ·
Maintainers usually reply within 2 days