| commit | 530fd851d1de8075e5d0e090f546b55226f69c9c | [log] [tgz] |
|---|---|---|
| author | Ignas Anikevicius <240938+aignas@users.noreply.github.com> | Fri Nov 17 04:18:43 2023 +0900 |
| committer | GitHub <noreply@github.com> | Thu Nov 16 19:18:43 2023 +0000 |
| tree | 19fdb6fc796a8ae2d25c5cedd6763469fbb0c869 | |
| parent | d96214fc1a7ec055848fc64793559bdfa39114a5 [diff] |
fix(bzlmod pip): ensure that sub-modules do not have invalid repos (#1549) This fixes the cases where the 'default_version' is passed to the 'render_pkg_aliases' utility but the 'default_version' is not present for the wheels. This usually happens when a sub-module is using the 'pip.parse' extension and the default_version can only be set by the root module. Previously, such a case would generate a `select()` expression that mapped the default condition to a non-existent target (because the sub-module didn't call `pip.parse()` with that version). This would either result in errors due the target not existing, or silently using a target intended for a different Python version (which may work, but isn't correct to so). Now, it results in a error via `select.no_match_error`. Fixes #1548.
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.
Currently, the core rules build into the Bazel binary, and the symbols in this repository are simple aliases. However, we are migrating the rules to Starlark and removing them from the Bazel binary. Therefore, the future-proof way to depend on Python rules is via this repository. SeeMigrating from the Bundled Rules below.
The core rules are stable. Their implementation in Bazel is subject to Bazel's backward compatibility policy. Once migrated to rules_python, they may evolve at a different rate, but this repository will still 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.