pip package rules for bazel that are fast (incremental fetch), support different python versions and work with all kinds of packages (i.e. packages with namespaces)
Certain packages require patches for their C++ extensions to work with bazel, or just in general for extra features. rules_pip can add a mechanism for applying patches and/or replacing BUILD files for dependencies, but I think it's best to allow users to use bazel's existing mechanisms and just defer to that.
Normally, users can just pull in a python package from pypi manually and use that, but if it's a dependency of another package, then rules_pip also pulls it in and risks multiple versions of the same dependency (or the same version but included from two paths).
Certain packages require patches for their C++ extensions to work with bazel, or just in general for extra features.
rules_pip
can add a mechanism for applying patches and/or replacing BUILD files for dependencies, but I think it's best to allow users to use bazel's existing mechanisms and just defer to that.Normally, users can just pull in a python package from pypi manually and use that, but if it's a dependency of another package, then
rules_pip
also pulls it in and risks multiple versions of the same dependency (or the same version but included from two paths).