| commit | 23da9a12fe58a1f4f4bf8a4a64aabf12c23ca592 | [log] [tgz] |
|---|---|---|
| author | Ignas Anikevicius <240938+aignas@users.noreply.github.com> | Tue Sep 16 11:55:46 2025 +0900 |
| committer | Ignas Anikevicius <240938+aignas@users.noreply.github.com> | Sun Sep 21 22:15:10 2025 +0900 |
| tree | f8f877846e9f01c349869cc9dc845b3803db59e5 | |
| parent | eed169034e989dc39b02a4e6a6767b3f59541ae0 [diff] |
fix(pypi): select the lowest available libc version by default (#3255) The #3058 PR has subtly changed the default behaviour of `experimental_index_url` code path and I think in order to make things easier by default for our users we should go back to that behaviour. And in addition to this we are starting to make use of the Minimal Version Selection algorithm for the platforms. This in general allows users to configure the upper platform version for a particular wheel. This meant that we had to change the semantics of the API a little: 1. Use MVS for each platform platform tag. 2. Make it such that earlier entries are overridden by later ones, i.e. `["musllinux_*_x86_64", "musllinux_1_2_x86_64"]` is effectively the same as just `["musllinux_1_2_x86_64"]`. A remaining thing that will be left as a followup for #2747 will be to figure out how to allow users to ignore certain platform tags. Fixes #3250 --------- Co-authored-by: Richard Levasseur <richardlev@gmail.com> Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Cherry-picked from 5fa1a87cd9d477311deaa6eb29e936c6ba7fd5fb
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.