You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Originally reported by: jaraco (Bitbucket: jaraco, GitHub: jaraco)
While developing setuptools 18.3.2 with
SETUPTOOLS_SYS_PATH_TECHNIQUE=raw
, I'll runsetup.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 ineasy-install.pth
. I had to delete the setuptools version found in site-packages before thedevelop
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.
The text was updated successfully, but these errors were encountered: