-
Notifications
You must be signed in to change notification settings - Fork 24
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
Please document example of namespace handling #35
Comments
i will check, but in the meanwhile look in |
it passes for me, on mac, python 3.8 |
also tested on linux |
I appreciate your quick reply. Can you confirm it is not leveraging your locally-installed packages? I found the issue is avoided and the build passes if either package is locally-installed on my build system and available on PYTHONPATH (ie not brought in hermetically by Bazel). Locally-installed non-hermetic packages are not the intention though. |
they are not |
it would be great if you can add Dockerfile to reproduce this |
Looks like I'm wrong; Sorry. Your very specific request (thanks) helped me find a possible solution (build host taint trashing the first resolution of the Bazel builds should be hermetic !
For the next person who has this issue (and for when I forget :-/ ) I'm documenting the path to the solution at https://github.com/chickenandpork/bazel-pip-import-namespace#recommendation |
Hey @ali5h, I've got an instance of the google.* and azure.* namespace clash issue (bazelbuild/rules_python#93 bazelbuild/rules_python#55). You've indicated that you fixed it, but the problem still persists in
v2.1.1
, can you give an idea of what that fix looks like?bazelbuild/rules_python#93 (comment)
as well bazelbuild/rules_python#93 (comment)
I'm using your latest release, and I'm still seeing the issue. Maybe there's additional text I've missed describing what else to do to activate this repair.
If you see https://github.com/chickenandpork/bazel-pip-import-namespace, it represents the issue I'm having. Note that transitory dependencies were tried as well, then commented back out in the
BUILD
file.bazel test //...
repro the error.I believe this follows the instructions you've shared. Can you see what else is missing to work around the issue ?
The text was updated successfully, but these errors were encountered: