develop command fails to take precedence when SETUPTOOLS_SYS_PATH_TECHNIQUE=raw
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: jaraco (Bitbucket: jaraco, GitHub: jaraco)
While developing setuptools 18.3.2 with SETUPTOOLS_SYS_PATH_TECHNIQUE=raw, I'll run setup.py develop but even after doing that, the installed version of setuptools is the version that appears in sys.path, even though the version under development is the one that appears in easy-install.pth. I had to delete the setuptools version found in site-packages before the develop version became present.
Possibly related is that zc.lockfile is also in easy-install.pth, and zc.lockfile has a dependency on setuptools.
I'll need to do more investigation and provide more information, but I wanted to register the issue as it's relevant to the opt-in functionality inspired by @minrk in Pull Request 135.
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 issue with setup.py develop while SETUPTOOLS_SYS_PATH_TECHNIQUE=raw, then inspect how the installed setuptools entry and easy-install.pth affect sys.path. Compare the behavior with zc.lockfile present; done means the development version takes precedence without manually deleting the installed version.
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