| commit | 5c3b71cbccd76b81243fddf2887fdfdd1a5735af | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Sun Oct 06 17:43:08 2024 -0700 |
| committer | GitHub <noreply@github.com> | Mon Oct 07 00:43:08 2024 +0000 |
| tree | d7a38a8da5f7a60e5f849a710d18ed2fbca58c3a | |
| parent | 9c3d303418a4eec0f701a8a46fb06b1aa7f7ea61 [diff] |
feat(toolchains): default py_runtime.implementation_name to cpython (#2272) This defaults `py_runtime.implementation_name` to `cpython`, the value that is most likely to be used. This is done not only because it's the most likely value, but because of how it affects whether precompiling works. Within py_runtime, automatically computing `pyc_tag` requires both `implementation_name` and Python version information. With upcoming changes to make `--python_version` always set to the correct value, it'll make enabling precompiling easier, especially if there are custom toolchains defined.
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.