Issue with Metadata Version Being Appended to Package Version in Shiv Build
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 114
- PR merge metrics
- No merged PRs in 30d
Description
Hello!
I’m experiencing an issue when building my Python project using shiv. My goal is to include both the package version and the Python version in the final shiv name. To do this, I’ve set up shiv to assess the pyproject.toml file to get the package version. However, I’ve noticed that shiv also pulls in the poetry metadata version and appends it to the package version without any separator. This results in a combined version string that’s confusing and not intended.
Is there a way to configure shiv to exclude the poetry metadata version, or to separate these versions properly?
Any guidance would be greatly appreciated!
Thank you!
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 reproducing the shiv build described in the issue, using the pyproject.toml package version and the requested Python version in the output name. Trace where shiv reads the package and Poetry metadata, then determine whether the appended version can be excluded or separated. Done means the resulting name contains the intended versions without an accidental concatenation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100