"build/lib" Directory is not cleaned up on bdist_wheel
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
The bdist_wheel command (and probably also other bdist* commands) could result in not-reproducible results:
- create project with file_a.py and file_b.py
- run setup.py bdist_wheel
- rename file_b.py to file_c.py
- run setup.py bdist_wheel (without touching "build" directory in the meantime)
- the resulting wheel will contain file_a.py, file_b.py and file_c.py
This is especially problematic when transforming a module from a single python file to a directory (or vice versa). In this case both module implementations are delivered.
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 sequence with setup.py bdist_wheel, renaming file_b.py to file_c.py without removing the build directory. Inspect how the build directory is reused during bdist_wheel and other bdist* commands; done means the resulting wheel contains only the current project files, without stale module implementations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100