Proper WSL support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 196
- PR merge metrics
- No merged PRs in 30d
Description
Right now, setting up keyring on WSL is complicated and some steps need to be done every time before a script using keyring can be launched:
https://github.com/jaraco/keyring/issues/566
It would be great if at least the steps that need to be done every time when running a keyring based script could be somehow encapsulated in keyring itself.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reading the setup steps and recurring commands described in linked issue #566, then compare them with keyring's existing WSL-related behavior. The issue does not name files, tests, or an entry point; completion would mean encapsulating the steps that must currently be repeated before each keyring-based script runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100