Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

develop command fails to take precedence when SETUPTOOLS_SYS_PATH_TECHNIQUE=raw #447

Open
ghost opened this issue Oct 11, 2015 · 1 comment

Comments

@ghost
Copy link

ghost commented Oct 11, 2015

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.


@dhood
Copy link

dhood commented Jul 12, 2017

This bug is impacting our project since SETUPTOOLS_SYS_PATH_TECHNIQUE=raw was set as the default in #674. We are setting it to rewrite as a workaround. Given that the environment variable seems slated for deprecation one day, we'd love to see this resolved before then! I've raised concern about the deprecation of that environment variable in #674 (comment); commenting here for visibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants