Confusing text in bazel.md

[mikegre-google]

📚 Documentation

The bazil.md file contains the following text:

Bazel brings in pybind11 embeded python and links against it to provide libpython to the plugin using this mechanism. Python headers are also sourced from there instead of depending on the system version. These are satisfied from the "@pybind11//:pybind11_embed", which sets up compiler options for linking with libpython transitively.

From what I can determine:

• pybind is a library of headers that defines an API for C++ and Python code to interact
• libpython is a library that provides the core implementation of the Python interpreter

The text above says "Bazel ... links against pybind to provide libpython to the plugin..."

• What does this mean?
• To what plugin does this refer?
• How does Bazel "provide libpython to the plugin"? Does this mean that Bazel uses the libpython library when building the plugin and the plugin uses the API defined in pybind to call into libpython? Why is it important to state how the plugin communicates with libpython?

The text says: "Python headers are also sourced from there instead of depending on the system version. "

• To where does "there" refer?

The text says: "These are satisfied from the "@pybind11//:pybind11_embed", which sets up compiler options for linking with libpython transitively."

• What does "these" refer to?
• What is "@pybind11//:pybind11_embed"?
• What does it mean to link with libpython transitively?

[miladm]

@ManfeiBai can you please help?

[mikegre-google]

bazel.md also states that TensorFlow is a Bazel external dependency and is configured in WORKSPACE, but I looked in pytorch/xla/WORKSPACE and didn't find a reference to TensorFlow. Is this information correct? I couldn't find another WORKSPACE file in the repo.