provide a mechanism for intentionally de-normalized versions (use-case nicely aligned date based calver)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 751
- Forks
- 324
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 3
Description
when using calver, we took notes of users of setuptools_scm (including myself at certain projects) to use versions like vYYYY.MM.DD.0
when always normalizing completely, this means that
this turns to
21.01.01 21.1.1
21.12.01 21.12.1
21.08.14 21.8.14
for date based versions im of the oppinion that they should nicely align, and fr that one needs leading zeroes
in setuptools_scm we currently prepare https://github.com/pypa/setuptools_scm/pull/584 to support this use-case
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 reviewing the existing version-normalization behavior described in the issue and the linked setuptools_scm pull request for the intended use case. Determine how packaging should represent intentionally de-normalized calendar versions, and define tests that show leading zeroes are preserved without breaking other version comparisons.
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