Bumps rules_python from 0.40.0 to 1.9.0.

Sourced from rules_python's releases.

1.9.0

For more detailed setup instructions, see https://rules-python.readthedocs.io/en/latest/getting-started.html

For the user-facing changelog see here

Using Bzlmod

Add to your MODULE.bazel file:

bazel_dep(name = "rules_python", version = "1.9.0")
python = use_extension("@​rules_python//python/extensions:python.bzl", "python")
python.toolchain(
python_version = "3.13",
)
pip = use_extension("@​rules_python//python/extensions:pip.bzl", "pip")
pip.parse(
hub_name = "pypi",
python_version = "3.13",
requirements_lock = "//:requirements_lock.txt",
)
use_repo(pip, "pypi")

Using WORKSPACE

Paste this snippet into your WORKSPACE file:

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
http_archive(
name = "rules_python",
sha256 = "098ba13578e796c00c853a2161f382647f32eb9a77099e1c88bc5299333d0d6e",
strip_prefix = "rules_python-1.9.0",
url = "https://github.com/bazel-contrib/rules_python/releases/download/1.9.0/rules_python-1.9.0.tar.gz",
)
load("@​rules_python//python:repositories.bzl", "py_repositories")
py_repositories()

Gazelle plugin

Paste this snippet into your WORKSPACE file:

... (truncated)

Sourced from rules_python's changelog.

1.9.0 - 2026-02-21

{#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.

... (truncated)

• bac5494 feat(pypi): make whl_library reproducible under pipstar (#3589) (#3632)
• 9a93adc chore: repleace version marker in features.bzl
• 0fafcd8 docs(gazelle): Add versionadded details to some Gazelle directives.md (#3624)
• 8a9cd71 chore: prepare 1.9.0 release (#3623)
• c805941 feat: command_line_option transition support, default windows to enable_runfi...
• 589c7ee build(deps): bump the pip group across 2 directories with 2 updates (#3617)
• b6f1b78 chore: better bootstrap logging (#3608)
• c9da781 fix: use runfiles_root_path in stage2 bootstrap (#3605)
• 16430a8 chore: ignore rmtree errors in wheel_installer_test (#3607)
• 1cfed94 test: add system_python_nodeps_test (#3609)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)