setuptools and state of PEP 376
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: cournape (Bitbucket: cournape, GitHub: cournape)
Hi there,
I was wondering whether the setuptools team were willing to support PEP 376 (adding .dist-info directories when doing python setup.py install) ?
The context: doing a python setup.py install for package foo and then later on doing a pip install foo does not work because the setup.py install step does not create a .dist-info directory, and in particular there is no RECORD file for pip to uninstall files. I would like to fix this as this has been a recurrent pain point in the scientific python community.
Also, what is the feeling around deprecating "egg dir install" so that by default python setup.py install would install foo in site-package/foo instead of site-packages/foo-1.0.egg ? Or is that considered too radical of a change ?
@ogrisel
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 reviewing PEP 376 and the existing python setup.py install behavior described in the issue. Determine the scope for creating .dist-info and a RECORD file, and separately clarify whether changing the default egg-directory installation is part of the work; done should include an agreed behavior and corresponding coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100