Allow `*` as third-party version
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.1k
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 82
Description
We have a few data-only packages (most recently tzdata) or calver packages where the API rarely changes (regex). I suggest we allow * as version for third-party packages. This will always use the full latest upstream version as part of the uploaded stubs. In the future, we could also extend the stub uploader to automatically upload a new stub version when a new upstream package is released.
This would make the version field match closer to what upstream version is actually supported and would reduce maintenance burden for maintainers.
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 the third-party stub uploader and the code that interprets the package version field. Trace how upstream versions are selected and recorded for uploaded stubs; done means * is accepted for third-party packages and uses the full latest upstream version without breaking existing version specifications.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100