| commit | e132012693f078d2bcbc359ae9b58a4d6d35b2ad | [log] [tgz] |
|---|---|---|
| author | Ignas Anikevicius <240938+aignas@users.noreply.github.com> | Mon Nov 10 10:34:59 2025 +0900 |
| committer | GitHub <noreply@github.com> | Mon Nov 10 01:34:59 2025 +0000 |
| tree | a9e06b2b70121e1461044623d9340c701bbf1b90 | |
| parent | 4fb634ebb9d07d50fd708d007cbf75d59e8094cc [diff] |
fix(pip): allow for different extras for different target platforms (#3385) With this PR we first evaluate the markers in the requirements files before going any further to aggregate them and process further. This makes the separation of logic a little bit more clear. I wanted to do this before I add more tests to after debugging the failures observed when enabling pipstar. Whilst cleaning up further I realized that I can fix the handling of packages where some platforms may end up not needing extras whilst others do. This is achieved by reusing the same code that allows us to have different versions per platform. Work towards #2949 Fixes #3374
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.