refactor: fold per-target python version into base rules (#2541) Today, specifying the Python version for a target requires using the version-aware rules in `transition.bzl` (or the generated equivalents bound to a specific Python version). With the rules rewritten in Bazel, that functionality can be moved into the base rules themselves. Moving the logic into the base rules simplifies the implementation and avoids having to re-implement subtle behaviors in the wrappers to correctly emulate the wrapped target. For backwards compatibility, the symbols in `transition.bzl` are left as aliases to the underlying rules.
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.