Installing typeshed stubs from lockfile
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 20.6k
- Forks
- 3.3k
- PR merge metrics
- PR metrics pending
Description
Feature
Abbility to install typeshed stubs from pylock.toml
Pitch
In our project we want to run mypy against system installed packages which vary on each distribution. We can create the pylock.toml file or equivalents from the current environment so we can have a list of all the installed packages. What we are missing though is a helper that would go through this list and install all possible stub files with appropriate version lock matching the installed ones so that it guarantees to not alter (upgrade/downgrade) the currently installed packages.
Contributor guide
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 locating mypy's existing handling of pylock.toml or equivalent lockfile data; the issue names no specific files or tests. Determine how installed packages and their versions can be matched to available typeshed stubs without changing those packages. Done means the helper installs compatible stubs while preserving the locked environment, with tests covering version matching and unavailable stubs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100