Discrepancy between setuptools and distutils in sdist without MANIFEST.in
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.9k
- Forks
- 1.4k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Originally reported by: ikelos (Bitbucket: ikelos, GitHub: ikelos)
This upstream bug (fixed in to 2010) resolved the need to create a MANIFEST.in file as well as list data_files in the setup.py. This does not appear to have been fixed in setuptools, and as such sdist and similar functions fail to include the appropriate files on machines that have setuptools, but not those that don't, when a fallback import system is used...
Would it be possible to align the two again so that setuptools is again a drop-in replacement for distutils?
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
Reproduce the sdist behavior described in the issue for a project without MANIFEST.in, comparing environments with and without setuptools. Trace how setuptools and distutils determine included data files; the work is done when both produce the appropriate files consistently without requiring MANIFEST.in.
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
- Needs clarification
- Newbie friendliness
- 25/100