| commit | 6d0d514c226f97728adea6dbdbd9bbde8804a0f0 | [log] [tgz] |
|---|---|---|
| author | Ignas Anikevicius <240938+aignas@users.noreply.github.com> | Tue Jan 09 09:22:47 2024 +0900 |
| committer | GitHub <noreply@github.com> | Tue Jan 09 00:22:47 2024 +0000 |
| tree | 5d95660df439cd9556fec40f5cc56128ac2ea371 | |
| parent | 3d68f6cc6b6c906cf5947b384cfba350810cf1fb [diff] |
refactor(pip_install): make the API surface of deps parsing smaller (#1657) With this change we also fix a minor bug where the self edge dependencies within the wheels are correctly handled as per unit tests. Also refactor the code to use the fact that the selects are chosen based on the specificity of the condition. This can make the addition of deps incrementally correct without the need for extra processing in the `build` method. This should hopefully make the implementation more future-proof as it makes use of these generic concepts and is likely to help to extend this code to work with selecting on multiple Python versions. I have added a test to ensure coverage of the new code.
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.