tag_build breaks prepare_metadata_for_build_wheel
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Previously reported in pypa/pip#9446.
This is similar to #1462, but for PEP 517 hooks, so I’m guessing a similar treatment is needed?
[egg_info]
tag_build = dev
[metadata]
name = pkg
version = 0.1
egg_info works as expected:
$ py -c 'from setuptools import *; setup()' egg_info >/dev/null
$ rg '^Version:' < pkg.egg-info/PKG-INFO
Version: 0.1.dev0
But not the PEP 517 hook:
$ py -c 'import os; from setuptools.build_meta import *; prepare_metadata_for_build_wheel(os.getcwd())' >/dev/null
$ rg '^Version:' < pkg.dist-info/METADATA
Version: 0.1.dev0dev
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
Start by reproducing the two commands in the issue and compare the version written to PKG-INFO with the version written to dist-info/METADATA. Trace the prepare_metadata_for_build_wheel entry point alongside egg_info, then consider the issue complete when both paths produce the expected 0.1.dev0 version for the sample configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100