Bump rules_python from 1.9.0 to 2.0.1

[dependabot]

Bumps rules_python from 1.9.0 to 2.0.1.

Release notes

Sourced from rules_python's releases.

2.0.1

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 = "2.0.1")
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 = "d4dd58e857a7c1bfc7da68adaef1178a20b197b1176c877afd2373369857e65c",
strip_prefix = "rules_python-2.0.1",
url = "https://github.com/bazel-contrib/rules_python/releases/download/2.0.1/rules_python-2.0.1.tar.gz",
)
load("@​rules_python//python:repositories.bzl", "py_repositories")
py_repositories()

Gazelle plugin

Paste this snippet into your WORKSPACE file:

... (truncated)

Changelog

Sourced from rules_python's changelog.

2.0.1 - 2026-05-08

{#v2-0-1-fixed}

Fixed

• (pypi) Fix the versions of packages that we are recording to a MODULE.bazel.lock file facts by passing all of the versions to the get_index function. Fixes #3756.
• (bzlmod) Reduce default verbosity of our loggers for non-root modules (#3749).

{#v2-0-0}

2.0.0 - 2026-04-09

{#v2-0-0-removed}

Removed

• Nothing removed.

{#v2-0-0-changed}

Changed

Breaking

• {obj}--windows_enable_symlinks is required. Add startup --windows_enable_symlinks to your .bazelrc to enable Bazel using full symlink support on Windows.
• venv-based binaries are created by default ({obj}--bootstrap_impl=system_python) on supported platforms (Linux/Mac with Bazel 8+, or Windows).
• --build_python_zip on Windows is ignored. Use {obj}py_zipapp_binary to create zips of Python programs.
• (pypi) Previously experimental_index_url users would not need to specify target platforms if cross-building is required. From now we will only pull wheels for the host OS to better align with how the rules work with the legacy pip implementation. Use {obj}pip.parse.target_platforms to customize the behavior. Related to #260.

Other changes:

• (pypi) Update dependencies used for compile_pip_requirements, building sdists in the whl_library rule and fetching wheels using pip.
• (pypi) Before using the bazel downloader to fetch the PyPI package metadata we will from now on fetch the lists of available packages on each index. The used package mappings will be written as facts to the MODULE.bazel.lock file on supported bazel versions and it should be done at most once. As a result, per-package {obj}experimental_index_url_overrides is no longer needed, but if specified, it needs to be provided for all packages not on the default index. What is more, the flags for --index_url and --extra-index-url now behave in the

... (truncated)

Commits

• e29c577 test: finish fixing the mocks in the pypi_cache
• ed05762 fix(test): update the lock-file to corresspond to the current deps
• 2852efd fix(logger): do not output WARN level logs for non-root modules (#3760)
• d876cfe fix(pypi): pass the correct versions to get_index_urls and fix cache invalida...
• 1390b36 fix(pypi): don't resolve python interpreter when not necessary (#3727)
• 91b3224 fix(pypi): build the environment on the fly (#3720)
• 577bb1f fix(pypi): correctly write the used facts back (#3719)
• 8c726cb fix(pypi): skip index lookups when all package overrides are specified (#3710)
• 8cc468b sphinxdocs: remove local rules_python dev overrides (#3705)
• 3949cca chore: have no-matching-distribution error message hint about target_platform...
• 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.

---

Dependabot commands and options

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)

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0c85e19870

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Update the git override with the version bump

This bump changes the requested module version to 2.0.1, but the adjacent git_override still pins rules_python to commit bac549496f67b9f0109d914319c09acf653ccdea, which the existing comment says is meant to stay pinned to the release source commit alongside the module version. In builds using Bzlmod overrides, Bazel will fetch the overridden Git source rather than the registry artifact, so this dependency remains on the old rules_python source while appearing to be upgraded.

Useful? React with 👍 / 👎.

[dependabot]

Superseded by #66.