Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Clean up version number handling for Python extension

Open
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
50/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
build-system, cli

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.

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.

Dominant language
C++
Stars
64
Forks
21
Avg merge
2d 17h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/VisualTrueType

All issues in microsoft/VisualTrueType

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.