experimental do not merge - rules_python update - autoclosed

[eclipse-score-bot]

This PR contains the following updates:

Package	Type	Update	Change
rules_python	bazel_dep	minor	1.8.3 → 1.9.0

🚨 EXPERIMENTAL DO NOT MERGE 🚨

This Renovate setup is currently under testing.

Contact #infrastructure if you have any questions or feedback.

---

Release Notes

bazel-contrib/rules_python (rules_python)

v1.9.0

Compare Source

{#v1-9-0-removed}

Removed

• Nothing removed.

{#v1-9-0-changed}

Changed

• DEPRECATED: implicit zipapp support
  • Implicit zipapp output of py_binary/py_test has been deprecated and
    replaced by separate {obj}py_zipapp_binary and {obj}py_zipapp_test
    rules. See
    #​3567
    for a detailed migration guide.
• (toolchains) stop exposing config settings in python toolchain alias repos.
  Please consider depending on the flags defined in
  //python/config_setting/... and the @platforms package instead.
• (binaries/tests) The PYTHONBREAKPOINT environment variable is automatically inherited
• (binaries/tests) The {obj}stamp attribute now transitions the Bazel builtin
  {flag}--stamp flag.
• (pypi) Now the RECORD file patches will follow the quoted or unquoted filenames convention
  in order to make pytorch and friends easier to patch.
• (wheel) py_wheel no longer expands the input depset during analysis,
  improving analysis performance for targets with large dependency trees.
• (binaries/tests) (Windows) --enable_runfiles=true is the default for
  py_binary/py_test. Prior behavior can be restored by adding
  @rules_python//command_line_option:enable_runfiles=false or
  @rules_python//command_line_option:enable_runfiles=INHERIT to the
  config_settings attribute. NOTE: enable_runfiles=true will
  soon become required for Windows.

{#v1-9-0-fixed}

Fixed

• (tests) No more coverage warnings are being printed if there are no sources.
  (#​2762)
• (gazelle) Ancestor conftest.py files are added in addition to sibling conftest.py.
  (#​3497) Note
  that this behavior can be reverted to the pre-1.9.0 behavior by setting the new
  python_include_ancestor_conftest directive to false.
• (binaries/tests) Stamped build data generated by Windows actions is readable

{#v1-9-0-added}

Added

• (binaries/tests) {obj}--debugger: allows specifying an extra dependency
  to add to binaries/tests for custom debuggers.
• (binaries/tests) Build information is now included in binaries and tests.
  Use the bazel_binary_info module to access it. The {flag}--stamp flag will
  add {obj}--workspace_status_command information.
• (gazelle) A new directive python_generate_pyi_srcs has been added. When
  true, a py_* target's pyi_srcs attribute will be set if any .pyi files
  that are associated with the target's srcs are present.
  (#​3354).
• (zipapp) {obj}py_zipapp_binary and {obj}py_zipapp_test rules added. These
  will replace --build_python_zip and the zip output group of
  py_binary/py_test. The zipapp rules support more functionality, correctness,
  and have better build performance.
• (toolchains) Added {obj}PyExecToolsInfo.exec_runtime for more easily
  getting an RBE-compatible runtime to use for build actions.
• (providers) {obj}PyExecutableInfo has several new fields to aid packaging
  of binaries: {obj}PyExecutableInfo.app_runfiles,
  {obj}PyExecutableInfo.interpreter_args,
  {obj}PyExecutableInfo.stage2_bootstrap, and
  {obj}PyExecutableInfo.venv_python_exe.
• (tools/wheelmaker.py) Added support for URL requirements according to PEP 508
  in Requires-Dist metadata. (#​3569)
• (gazelle) A new directive python_include_ancestor_conftest has been added.
  When false, ancestor conftest targets are not automatically added to
  {bzl:obj}py_test target dependencies. This false behavior is how things
  were in rules_python before 1.9.0. The default is true, as the prior behavior
  was technically incorrect.
  (#​3596)

{#v1-8-5}

v1.8.5

Compare Source

{#v1-8-5-fixed}

Fixed

• (runfiles) Fixed CurrentRepository() raising ValueError on Windows.
  (#​3579)
• (pypi) pip_parse no longer silently drops PEP 508 URL-based requirements
  (pkg @​ https://...) when extract_url_srcs=False (the default for
  pip_repository).
• (pypi) Extras in requirement strings are now normalized per PEP 685,
  fixing missing transitive dependencies when extras contain hyphens
  (e.g., sqlalchemy[postgresql-psycopg2binary]).
  (#​3587)

{#v1-8-4}

v1.8.4

Compare Source

{#v1-8-4-fixed}

Fixed

• (pipstar): A corner case of evaluation of version specifiers ("1.2" ~= "1.2.0")
  has been fixed improving compatibility with the PEP440 standard.
  Fixes #​3580.
• (pipstar): We now add read permissions after extracting wheels for the cases
  where the whl file is missing them.
  Fixes #​3554.

{#v1-8-3}

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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 Renovate Bot.

[eclipse-score-bot]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: MODULE.bazel.lock

Command failed: bazel mod deps --lockfile_mode=update
 no actions running
DEBUG: /tmp/containerbase/cache/.cache/bazel/_bazel_ubuntu/636dba5dea2585a0640767eee1a6bc02/external/rules_jvm_external+/private/extensions/maven.bzl:155:14: The maven repository 'maven' is used in two different bazel modules, originally in 'protobuf' and now in 'grpc-java'
 no actions running
ERROR: @@bazel_tools//tools/cpp:cc_configure.bzl does not export a module extension called cc_configure_extension, yet its use is requested at https://bcr.bazel.build/modules/abseil-cpp/20240722.0/MODULE.bazel:23:29
ERROR: module extension @@grpc+//bazel:grpc_deps.bzl%grpc_repo_deps_ext does not generate repository "com_envoyproxy_protoc_gen_validate", yet it is imported as "com_envoyproxy_protoc_gen_validate" in the usage at https://bcr.bazel.build/modules/grpc-java/1.66.0/MODULE.bazel:68:35
ERROR: Results may be incomplete as 2 extensions failed.

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //src:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.4.2) and connecting to it...
INFO: Invocation ID: 9ee9bfe2-85eb-4dcb-8e80-0699ca7ef3ae
Computing main repo mapping: 
ERROR: Error computing the main repository mapping: Missing checksum for registry file https://raw.githubusercontent.com/eclipse-score/bazel_registry/main/modules/rules_python/1.9.0/MODULE.bazel not permitted with --lockfile_mode=error. Please run `bazel mod deps --lockfile_mode=update` to update your lockfile.