Python version 3.12rc1 - cannot find backend (Windows 11) and fatal exception in set

Open
#648 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend, security

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

Windows
  1. keyring list-backends gives nothing when installed on a Python 3.12-rc1 virtual environment.
  2. 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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jaraco/keyring

All issues in jaraco/keyring

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.