Disable nspkg.pth magic when PEP-420 is available #805
Comments
Turns out the implementation is pretty straightforward. In the 'issue-805' branch, I've committed probably the minimal changes to support this functionality. I've tagged and released these changes as 28.1.0b1, a wheel that I've hosted here. I've confirmed the technique works. I'm going to run with this version of setuptools for a while and see if I encounter any issues. I invite others to try it out as well. Just:
|
Merging with v28.1.0, I've cut a new wheel of 28.2.0b1:
|
This was referenced Oct 13, 2016
jaraco
added a commit
that referenced
this issue
Nov 13, 2016
jaraco
added a commit
that referenced
this issue
Nov 13, 2016
jaraco
added a commit
that referenced
this issue
Dec 11, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In pypa/pip#1924, we find that setuptools is generating the
-nspkg.pth
files that are bootstrapping the namespace packages, but these files are unnecessary when PEP-420 is present (Python 3.3+) and in fact interfere with pure PEP-420 namespace packages.It seems the solution may be simple - bypass this behavior when PEP-420 is detected.
The text was updated successfully, but these errors were encountered: