microsoft / microsoft/VisualTrueType
Clean up version number handling for Python extension
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 64
- Forks
- 21
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 3
Description
Currently version number is set in setup.py which is used when extension is built and vttcompilepy/_version.py that is used in response to --version argument. Combine and/or use use_scm_version to reconcile version number.
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
Read setup.py and vttcompilepy/_version.py first, then compare how the extension build obtains its version with how --version reports it. Verify the chosen source is used consistently in both paths; done means the two version values no longer need separate maintenance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, cli
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100