| commit | 2c7187d6558ce39e1bd2fea4c0637722258f7790 | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <richardlev@gmail.com> | Tue Jul 15 22:34:01 2025 -0700 |
| committer | GitHub <noreply@github.com> | Wed Jul 16 05:34:01 2025 +0000 |
| tree | 15c38dc08d31e9bd805b05f40a0f721acd6fc263 | |
| parent | cab415d82ebbfd1b8b2d81ef61baf3f9a274a1b2 [diff] |
fix: support debian multiarch with local toolchains (#3100) Apparently, there is a "multiarch" style of Python installations, where the shared libraries can be in a sub-directory. The best docs I could find about this are https://wiki.debian.org/Python/MultiArch. To fix, looking at the `MULTIARCH` sysconfig var tells what subdirectory, if any should be looked in. Along the way, fix a changelog issue reference url. Fixes https://github.com/bazel-contrib/rules_python/issues/3099
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.