Conversation
This fixes an issue where if you have bad URLs in your ~/.pip/pip.conf, pip would pick them up and end up failing bazel. This way we make pip_import more hermetic and ignore user config.
|
Thanks for the change. Will merge shortly. |
b8a8529 to
1ff274c
Compare
|
Thanks!
|
This fixes the same issue as bazel-contrib#232 but in another place.
This fixes the same issue as bazel-contrib#232 but in another place.
This fixes the same issue as #232 but in another place. Co-authored-by: Jonathon Belotti <[email protected]>
|
Can we do it configurable/revert? It breaks previous behavior. I use |
|
I think it would be fine to configure if the maintainers are ok with another option for that, you can probably workaround this in the meantime by passing |
|
@keith in my case I also need an user/password pair to use PyPI repo: |
|
@slsyy I don't have an immediate solution, but could any of these approaches work for you? bazel-contrib/rules_jvm_external#80 (comment) |
This fixes an issue where if you have bad URLs in your ~/.pip/pip.conf,
pip would pick them up and end up failing bazel. This way we make
pip_import more hermetic and ignore user config.
You can reproduce this issue by adding:
To your local
~/.pip/pip.conf, and executing apip_importrule (it fails faster if your URL returns 500s rather than is just unaccessible)