Use rules_python in Bazel builds #821
Labels
area/code-health
Concerns stability, quality, technical debt, etc.
area/dependencies
Concerns libraries or other software that TFQ depends on
area/installation
Concerns installation of TFQ
priority/p2
Next release should contain it
The consensus is that the right way to build Python software with Bazel is to use bazelbuild/rules_python. Bazel doesn't see changes in the Python environment installed by pip or elsewhere; it's only aware of things that are "imported" into it.
Doing this will take some work in figuring out how to avoid replicating the contents of requirements.txt in the Bazel files, so that we maintain one source of truth for the Python dependencies.
The text was updated successfully, but these errors were encountered: