Provide a way to distinguish between dev-only releases and dev release of a pre-release
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 751
- Forks
- 324
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 3
Description
As this question has come up a couple of times now I created such discussion: https://discuss.python.org/t/are-developmental-releases-a-type-of-pre-release/81666
If it's decided that dev-releases are a form of pre-release then one thing missing from packaging's current API is a way to distguish between a dev-release of a final release, and a dev-release of a pre-release, e.g.
1.0dev1and1.0a1dev1.
Originally posted by @notatallshaw in #875
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 with the linked Python discussion and issue #875 to determine whether development releases are pre-releases and what distinction the API should expose. No implementation file or test is named; done means agreeing on behavior that distinguishes examples such as 1.0dev1 and 1.0a1dev1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100