-
-
Notifications
You must be signed in to change notification settings - Fork 261
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
Bad installed_wheels
dir when a wheel's top_level.txt
dirname collides with sources
#2160
Comments
There is a bit of chaff in the example. The key bit is With just
And that should be enough to see the issue. Now, for 3rdparty deps, this sort of collision (namespace package) is handled via a So, to handle this case where the namespace package is split across |
The issue you're going to run into here though @thejcannon that Pex can't help you with is your example is not properly ns-packaged. The sources are (lack of |
Previously namespace packages were handled only amongst 3rd-party deps. Any ns-package also split across PEX user sources would lead to one of the 3rd-party dep members of the namespace package getting its cached wheel install contaminated with the PEX user source that was a member of the ns-package. Fixes pex-tool#2160
I used this example, but with the ns-package issue fixed. |
Previously namespace packages were handled only amongst 3rd-party deps. Any ns-package also split across PEX user sources would lead to one of the 3rd-party dep members of the namespace package getting its cached wheel install contaminated with the PEX user source that was a member of the ns-package. Fixes #2160
Steps to reproduce:
Here's a
pex
(renamed to.zip
for GitHub's sake) local.zip. It has atop_level.txt
oftop_level
. Rename tolocal.whl
Then, next to that file:
mymain.py
is not part of the wheel, and shouldn't be in there.The text was updated successfully, but these errors were encountered: