bazelbuild/rules_python (rules_python)
### [`v0.29.0`](https://togithub.com/bazelbuild/rules_python/blob/HEAD/CHANGELOG.md#0290---2024-01-22)
[Compare Source](https://togithub.com/bazelbuild/rules_python/compare/0.28.0...0.29.0)
[0.29.0]: https://togithub.com/bazelbuild/rules_python/releases/tag/0.29.0
##### Changed
- **BREAKING** The deprecated `incompatible_generate_aliases` feature flags
from `pip_parse` and `gazelle` got removed. They had been flipped to `True`
in 0.27.0 release.
- **BREAKING** (wheel) The `incompatible_normalize_name` and
`incompatible_normalize_version` flags have been removed. They had been
flipped to `True` in 0.27.0 release.
- (bzlmod) The pip hub repository now uses the newly introduced config settings
using the `X.Y` python version notation. This improves cross module
interoperability and allows to share wheels built by interpreters using
different patch versions.
##### Fixed
- (bzlmod pip.parse) Use a platform-independent reference to the interpreter
pip uses. This reduces (but doesn't eliminate) the amount of
platform-specific content in `MODULE.bazel.lock` files; Follow
[#1643](https://togithub.com/bazelbuild/rules_python/issues/1643) for removing
platform-specific content in `MODULE.bazel.lock` files.
- (wheel) The stamp variables inside the distribution name are no longer
lower-cased when normalizing under PEP440 conventions.
##### Added
- (toolchains) `python_register_toolchains` now also generates a repository
that is suffixed with `_host`, that has a single label `:python` that is a
symlink to the python interpreter for the host platform. The intended use is
mainly in `repository_rule`, which are always run using `host` platform
Python. This means that `WORKSPACE` users can now copy the `requirements.bzl`
file for vendoring as seen in the updated `pip_parse_vendored` example.
- (runfiles) `rules_python.python.runfiles.Runfiles` now has a static `Create`
method to make imports more ergonomic. Users should only need to import the
`Runfiles` object to locate runfiles.
- (toolchains) `PyRuntimeInfo` now includes a `interpreter_version_info` field
that contains the static version information for the given interpreter.
This can be set via `py_runtime` when registering an interpreter toolchain,
and will done automatically for the builtin interpreter versions registered via
`python_register_toolchains`.
Note that this only available on the Starlark implementation of the provider.
- (config_settings) Added `//python/config_settings:is_python_X.Y` config
settings to match on minor Python version. These settings match any `X.Y`
version instead of just an exact `X.Y.Z` version.
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
0.28.0->0.29.0Release Notes
bazelbuild/rules_python (rules_python)
### [`v0.29.0`](https://togithub.com/bazelbuild/rules_python/blob/HEAD/CHANGELOG.md#0290---2024-01-22) [Compare Source](https://togithub.com/bazelbuild/rules_python/compare/0.28.0...0.29.0) [0.29.0]: https://togithub.com/bazelbuild/rules_python/releases/tag/0.29.0 ##### Changed - **BREAKING** The deprecated `incompatible_generate_aliases` feature flags from `pip_parse` and `gazelle` got removed. They had been flipped to `True` in 0.27.0 release. - **BREAKING** (wheel) The `incompatible_normalize_name` and `incompatible_normalize_version` flags have been removed. They had been flipped to `True` in 0.27.0 release. - (bzlmod) The pip hub repository now uses the newly introduced config settings using the `X.Y` python version notation. This improves cross module interoperability and allows to share wheels built by interpreters using different patch versions. ##### Fixed - (bzlmod pip.parse) Use a platform-independent reference to the interpreter pip uses. This reduces (but doesn't eliminate) the amount of platform-specific content in `MODULE.bazel.lock` files; Follow [#1643](https://togithub.com/bazelbuild/rules_python/issues/1643) for removing platform-specific content in `MODULE.bazel.lock` files. - (wheel) The stamp variables inside the distribution name are no longer lower-cased when normalizing under PEP440 conventions. ##### Added - (toolchains) `python_register_toolchains` now also generates a repository that is suffixed with `_host`, that has a single label `:python` that is a symlink to the python interpreter for the host platform. The intended use is mainly in `repository_rule`, which are always run using `host` platform Python. This means that `WORKSPACE` users can now copy the `requirements.bzl` file for vendoring as seen in the updated `pip_parse_vendored` example. - (runfiles) `rules_python.python.runfiles.Runfiles` now has a static `Create` method to make imports more ergonomic. Users should only need to import the `Runfiles` object to locate runfiles. - (toolchains) `PyRuntimeInfo` now includes a `interpreter_version_info` field that contains the static version information for the given interpreter. This can be set via `py_runtime` when registering an interpreter toolchain, and will done automatically for the builtin interpreter versions registered via `python_register_toolchains`. Note that this only available on the Starlark implementation of the provider. - (config_settings) Added `//python/config_settings:is_python_X.Y` config settings to match on minor Python version. These settings match any `X.Y` version instead of just an exact `X.Y.Z` version.Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.