Removed

• (toolchain) Remove all of the python 3.8 toolchain support out of the box. Users needto pass theTOOL_VERSIONS that include 3.8 toolchains or use thebzlmod APIs to addthem back. This means any hubpip.parse calls that target3.8 will be ignored fromnow on. (#2704)

• (toolchain) Remove all of the python 3.9 toolchain versions except for the3.9.25.This version has reached EOL and will no longer receive any security fixes, please update to3.10 or above. (#2704)

• (toolchain)ignore_root_user_error has now been flipped to be always enabled andthechmod of the python toolchain directories have been removed. From now onrules_pythonalways adds thepyc files to the glob excludes and in order to avoid any problems when usingthe toolchains in the repository phase, ensure that you pass-B to the python interpreter.(#2016)

Changed

• (toolchains) Use toolchains from the20251031 release.

• (gazelle) Internally split modules mapping generation to be per-wheel for concurrency and caching.

• (pip)pipstar has been enabled for allwhl_library instances where the whlis passed through a label or downloaded using the bazel downloader(#2949).

Fixed

• (gazelle) Removepy_binary targets with invalidsrcs. This includes filesthat are not generated or regular files.

• (runfiles) Fix incorrect Python runfiles path assumption - the existingimplementation assumes that it is always four levels below the runfilesdirectory, leading to incorrect path checks(#3085).

• (toolchains) local toolchains now tell thesys.abiflags value of theunderlying runtime.

• (toolchains) various local toolchain fixes: add abi3 header targets,fixes to linking, Windows DLL detection, and defines for free threadedruntimes.

• (toolchains) Thepython_headers target is now compatible withlayering_check.

• (performance) 90% reduction in py_binary/py_test analysis phase cost.(#3381).

• (gazelle) Fixgazelle_python_manifest.test so that it accesses manifest files viarunfile path handling rather than directly (#3397).

• (core rules) For the system_python bootstrap, the runfiles root is added tosys.path.

Added

• (toolchains)3.9.25 Python toolchain from20251031 release.

Removed

• (core rules) Support for Bazel’s long deprecated “extra actions” has beenremoved(#3215).

Changed

• (deps) bumped rules_cc dependency to0.1.5.

• (bootstrap) For--bootstrap_impl=system_python,PYTHONPATH is nolonger used to add import paths. The sys.path order has changed from[apppaths,stdlib,runtimesite-packages] to[stdlib,apppaths,runtimesite-packages].

• (bootstrap) For--bootstrap_impl=system_python, the sys.path order haschanged from[apppaths,stdlib,runtimesite-packages] to[stdlib,apppaths,runtimesite-packages].

• (pip) Publishing deps are no longer pulled viaexperimental_index_url.(#2937).

• (toolchains)py_runtime andPyRuntimeInfo reject Python 2 settings.Settingpy_runtime.python_version="PY2" or non-NonePyRuntimeInfo.py2_runtime is an error.

• (pypi)pipstar flag has been implemented forWORKSPACE and can be flipped to be enabled usingRULES_PYTHON_ENABLE_PIPSTAR=1 environment variable. If you do, pleaseadd a comment to#2949 if you run into anyproblems.With this release we are deprecatingpip.parse.experimental_target_platforms andpip_repository.experimental_target_platforms. For users usingWORKSPACE andvendoring therequirements.bzl file, please re-vendor so that downstream is unaffectedwhen the APIs get removed. If you need to customize the way the dependencies getevaluated, seeour docs on customizingRequires-Dist resolution.

• (toolchains) Added Python versions 3.15.0a1, 3.14.0, 3.13.9, 3.12.12, 3.11.14, 3.10.19, and 3.9.24from the20251014 release.

• (deps) (bzlmod) Upgraded tobazel-skylib version1.8.2

Fixed

• (rules) ThePyInfo constructor was setting the wrong value forhas_py3_only_sources - this is now fixed.

• (bootstrap) The stage1 bootstrap script now correctly handles nestedRUNFILES_DIRenvironments, fixing issues where apy_binary calls anotherpy_binary(#3187).

• (bootstrap) For Windows, having many dependencies no longer results in maxlength errors due to too long environment variables.

• (bootstrap)--bootstrap_impl=script now supports the-S interpretersetting.

• (venvs)--venvs_site_packages=yes no longer errors when packages withoverlapping files or directories are used together.(#3204).

• (venvs)--venvs_site_packages=yes works for packages that dynamicallylink to shared libraries(#3228).

• (venvs)--venvs_site_packages=yes includespth files at the root of thesite-packages folder(#3339).

• (uv)//python/uv:lock.bzl%lock now works with a local platformruntime.

• (pypi)linux_riscv64 is added to the platforms list in_pip_repository_impl,which fixesa build issue for tensorflow on riscv64.

• (toolchains) WORKSPACE builds now correctly register musl and freethreadedvariants. Setting--py_linux_libc=musl and--py_freethreaded=yes nowactivate them, respectively.(#3262).

• (rules)py_console_script_binary is now compatible with symbolic macros(#3195).

Added

• (runfiles) The Python runfiles library now supports Bazel’s--incompatible_compact_repo_mapping_manifest flag.

• (bootstrap)--bootstrap_impl=system_python now supports themain_module attribute.

• (bootstrap)--bootstrap_impl=system_python now supports theRULES_PYTHON_ADDITIONAL_INTERPRETER_ARGS environment variable.

• (rules) Thepy_binary,py_test, andpy_wheel rules now have aconfig_settings attribute to control build flags within the build graph.Custom settings can be added usingconfig.add_transition_setting inMODULE.bazel files, orpy_repositories(transition_settings=...) inWORKSPACE files. See theHow to use a common set of dependencies with multiple PyPI versions guide on using commondependencies with multiple PyPI versions` for an example.

• (toolchains) Stable ABI headers support added. To use, depend on//python/cc:current_py_cc_headers_abi3. This allows Windows buildsa way to depend on headers without the potentially Python unstable ABIobjects from the regular//python/cc:current_py_cc_headers targetbeing included.

  • Adds//python/cc:current_py_cc_headers_abi3,py_cc_toolchain.headers_abi3, andPyCcToolchainInfo.headers_abi3.

  • //python:features.bzl%features.headers_abi3 can be used tofeature-detect the presense of the above.

• (toolchains) Local toolchains can use a label for the interpreter to use.

• (pypi) Support for environment marker handling andexperimental_index_url handling forWindows ARM64 for Python 3.11 and later(#2276).

Fixed

• (pypi) We now use the Minimal Version Selection (MVS) algorithm to selectthe right wheel when there are multiple wheels for the target platform(e.g.musllinux_1_1_x86_64 andmusllinux_1_2_x86_64). If the userwants to set the minimum version for the selection algorithm, use thepip.defaults.whl_platform_tags attribute to configure that. Ifmusllinux_*_x86_64 is specified, we will choose the lowest availablewheel version. Fixes#3250.

Changed

• (gazelle) update minimum gazelle version to 0.36.0 - may cause BUILD file changes

• (gazelle) update minimum rules_go version to 0.55.1

• (gazelle) remove custom go-tree-sitter module BUILD file

• (gazelle) For package mode, resolve dependencies when imports are relativeto the package path. This is enabled via the#gazelle:python_experimental_allow_relative_imports true directive (#2203 issue).

• (gazelle) Types for exposed members ofpython.ParserOutput are now all public.

• (gazelle) Removed the requirement for__init__.py,__main__.py, or__test__.py files to bepresent in a directory to generate aBUILD.bazel file.

• (toolchain) Updated the following toolchains to build20250808 to patch CVE-2025-47273:

  • 3.9.23

  • 3.10.18

  • 3.11.13

  • 3.12.11

  • 3.14.0rc1

• (toolchain) Python 3.13 now references 3.13.6

• (gazelle) Switched back to smacker/go-tree-sitter, fixing#2630

• (pypi) From now on the list of default platforms only includeslinux_x86_64,linux_aarch64,osx_x86_64,osx_aarch64 andwindows_x86_64. If you are on other platforms, you need touse thepip.default to configure it yourself. If you are interested in graduating theplatform, consider helping set us up CI for them and update the documentation.

• (ci) We are now testing on Ubuntu 22.04 for RBE and non-RBE configurations.

• (core)#!/usr/bin/envbash is now used as a shebang in the stage1 bootstrap template.

• (gazelle:docs) The Gazelle docs have been migrated fromgazelle/README.md togazelle/docs and are now available on the primary documentation siteat https://rules-python.readthedocs.io/en/latest/gazelle/docs/index.html

Fixed

• (toolchains)local_runtime_repo now respects changes to theDEVELOPER_DIR andXCODE_VERSIONrepo env vars, fixing stale cache issues on macOS with system (i.e. Xcode-supplied) Python(#3123).

• (pypi) Fixes an issue where builds using abazelvendor vendor directorywould fail if the constraints file contained environment markers. Fixes#2996.

• (pypi) Wheels with BUILD.bazel (or other special Bazel files) no longerresult in missing files at runtime(#2782).

• (runfiles) The pypi runfiles package now includespy.typed to indicate itsupports type checking(#2503).

• (pypi) The pipstardefaults configuration now supports any custom platformname.

• (pypi) The selection of the whls has been changed and should no longer resultin ambiguous select matches (#2759 issue) and should be much more efficientwhen runningbazelquery due to fewer repositories being included(#2849 issue).

• Multi-line python imports (e.g. with escaped newlines) are now correctly processed by Gazelle.

• (toolchains)local_runtime_repo works with multiarch Debian with Python 3.8(#3099).

• (pypi) Expose pypi packages only common to all Python versions inall_requirements(#2921).

• (repl) Normalize the path for theREPL stub to make it possible to use thedefault stub template from outsiderules_python (#3101 issue).

• (gazelle) Fixes gazelle adding sibling module dependencies to resolveabsolute imports (Python 2’s behavior withoutabsolute_import). Previousbehavior can be restored using the directive#gazelle:python_resolve_sibling_importstrue

• (pypi) Show overridden index URL of packages when downloading metadata have failed.(#2985).

• (toolchains) use “command -v” to find interpreter in$PATH(#3150).

• (pypi)bazelvendor now works inbzlmod (#3079 issue).

• (toolchains)local_runtime_repo now works on Windows(#3055).

• (toolchains)local_runtime_repo supports more types of Pythoninstallations (Mac frameworks, missing dynamic libraries, and otheresoteric cases, see#3148 for details).

• (pypi) Supportrequirements.txt files that use different versions of the samepackage targeting different target platforms.(#2797).

• (py_wheel) Add directories in deterministic order.

Added

• (repl) Default stub now has tab completion, wherereadline support is available,see (#3114).(#3114).

• (pypi) To configure the environment forrequirements.txt evaluation, use the newly addeddeveloper preview of thepip.default tag class. Onlyrules_python and root modules can usethis feature. You can also configure customconfig_settings usingpip.default. Itcan also be used to set the globalnetrc orauth_patterns variables.

• (pypi) PyPI dependencies now expose an:extracted_whl_files filegroup targetof all the files extracted from the wheel. This can be used in lieu ofwhl_filegroup to avoid copying/extracting wheel multiple times toget a subset of their files.

• (gazelle) New directivegazelle:python_generate_pyi_deps; whentrue,dependencies added to satisfy type-only imports (ifTYPE_CHECKING) and typestub packages are added topyi_deps instead ofdeps.

• (toolchain) Add toolchains for aarch64 windows for

  • 3.11.13

  • 3.12.11

  • 3.13.6

  • 3.14.0rc1

• (gazelle): New annotationgazelle:include_pytest_conftest. When not set (thedefault) ortrue, gazelle will inject anyconftest.py file found in the samedirectory as apy_test target to thatpy_test target’sdeps.This behavior is unchanged from previous versions. Whenfalse, the:conftestdep is not added to thepy_test target.

• (gazelle) New directivegazelle:python_generate_proto; whentrue,Gazelle generatespy_proto_library rules forproto_library.false by default.

  • Note: Users must manually configure their Gazelle target to support theproto language.

• (gazelle) New directivegazelle:python_proto_naming_convention; controlsnaming ofpy_proto_library rules.

Removed

• Nothing removed.

Fixed

• (toolchains)local_runtime_repo now checks if the include directory existsbefore attempting to watch it, fixing issues on macOS with system Python(#3043).

Fixed

• (toolchains)local_runtime_repo now checks if the include directory existsbefore attempting to watch it, fixing issues on macOS with system Python(#3043).

Changed

• (deps) (bzlmod) Upgraded tobazel-skylib version1.8.1to remove deprecation warnings.

Fixed

• (pypi) Correctly pullsdist distributions usingpip(#3131).

• (core) builds work again on7.xWORKSPACE configurations(#3119).

Fixed

• (pypi) Namespace packages work by default (pkgutil shims are generatedby default again)(#3038).

Changed

• (toolchain) Bundled toolchain version updates:

  • 3.9 now references 3.9.23

  • 3.10 now references 3.10.18

  • 3.11 now references 3.11.13

  • 3.12 now references 3.12.11

  • 3.13 now references 3.13.4

• (rules) On Windows,--bootstrap_impl=system_python is forced. Thisallows setting--bootstrap_impl=script in bazelrc for mixed-platformenvironments.

• (rules)compile_pip_requirements now generates a.test target. The_test target is deprecated and will be removed in the next major release.(#2794

• (py_wheel) py_wheel always creates zip64-capable wheel zips

• (providers) (experimental)PyInfo.venv_symlinks replacesPyInfo.site_packages_symlinks

• (deps) Updated setuptools to 78.1.1 to patch CVE-2025-47273. This effectively makesPython 3.9 the minimum supported version for usingpip_parse.

Fixed

• (rules) PyInfo provider is now advertised by py_test, py_binary, and py_library;this allows aspects using required_providers to function correctly.(#2506).

• Fixes when using--bootstrap_impl=script:

  • compile_pip_requirements now works with it

  • Thesys._base_executable value will reflect the underlying interpreter,not venv interpreter.

  • The//python/runtime_env_toolchains:all toolchain now works with it.

• (rules) Better handle flakey platform.win32_ver() calls by calling themmultiple times.

• (tools/wheelmaker.py) Extras are now preserved in Requires-Dist metadata when using requires_fileto specify the requirements.

• (pypi) Use bazel downloader for direct URL references and correctly detect the filenames fromvarious URL formats - URL encoded version strings get correctly resolved, sha256 value can bealso retrieved from the URL as opposed to only the--hash parameter. Fixes#2363.

• (pypi)whl_library now infers file names from itsurls attribute correctly.

• (pypi) When running underbazeltest, be sure that temporaryrequirements fileremains writable.

• (py_test, py_binary) Allow external files to be used for main

• (pypi) Correctly aggregate the sources when the hashes specified in the lockfile differby platform even though the same version is used. Fixes#2648.

• (pypi)compile_pip_requirements test rule works behind the proxy

• (toolchains) The hermetic toolchains now correctly statically advertise thereleaselevel andserial for pre-release hermetic toolchains (#2837 issue).

Added

• Repo utilitiesexecute_unchecked,execute_checked, andexecute_checked_stdout nowsupportlog_stdout andlog_stderr keyword arg booleans. When these areTrue(the default), the subprocess’s stdout/stderr will be logged.

• (toolchains) Local toolchains can be activated with custom flags. See[Conditionally using local toolchains] docs for how to configure.

• (pypi) Starlark-based evaluation of environment markers (requirements.txt conditionals)available (not enabled by default) for improved multi-platform build support.Set theRULES_PYTHON_ENABLE_PIPSTAR=1 environment variable to enable it.

• (utils) Add a way to run a REPL for anyrules_python target that returnsaPyInfo provider.

• (uv) Handle.netrc andauth_patterns auth when downloadinguv. Work towards#1975.

• (toolchains) Arbitrary python-build-standalone runtimes can be registeredand activated with custom flags. See the [Registering custom runtimes]docs andsingle_version_platform_override() API docs for moreinformation.

• (rules) Added support for a using constraints files withcompile_pip_requirements.Useful when an intermediate dependency needs to be upgraded to pull insecurity patches.

• (toolchains): 3.14.0b2 has been added as a preview.

Removed

• Nothing removed.

Fixed

• (toolchains)local_runtime_repo now checks if the include directory existsbefore attempting to watch it, fixing issues on macOS with system Python(#3043).

Fixed

• (pypi) Fix a typo not allowing users to benefit from using the downloader when the hashes in therequirements file are not present. Fixes#2863.

Changed

• (toolchain) Theexec configuration toolchain now has the forwardedexec_interpreter now also forwards theToolchainInfo provider. This isfor increased compatibility with theRBE setups where access to theexecconfiguration interpreter is needed.

• (toolchains) Use the latest astral-sh toolchain release20250317 for Python versions:

  • 3.9.21

  • 3.10.16

  • 3.11.11

  • 3.12.9

  • 3.13.2

• (pypi) Usexcrunxcodebuild--showsdks to find XCode root.

• (toolchains) Remove all but3.8.20 versions of the Python3.8 interpreter who hasreached EOL. If users still need other versions of the3.8 interpreter, please supplythe URLs manuallypython.toolchain orpython_register_toolchains calls.

• (toolchains) Previously#2636changed the semantics ofignore_root_user_error from “ignore” to “warning”. This is nowflipped back to ignoring the issue, and will only emit a warning when the attribute is setFalse.

• (pypi) The PyPI extension will no longer write the lock file entries as theextension has been marked reproducible.Fixes#2434.

• (gazelle) Lazily load and parse manifest files when running Gazelle. This ensures nomanifest files are loaded when Gazelle is run over a set of non-python directoriesPR #2746.

• (rules)py_binary.srcs andpy_test.srcs is no longer mandatory whenmain_module is specified (for--bootstrap_impl=script)

Fixed

• (pypi) Platform specific extras are now correctly handled when usinguniversal lock files with environment markers. Fixes#2690.

• (runfiles) (--bootstrap_impl=script) Follow symlinks when searching for runfiles.

• (toolchains) Do not try to runchmod when downloading non-windows hermetic toolchainrepositories on Windows. Fixes#2660.

• (logging) Allow repo rule logging level to be set toFAIL via theRULES_PYTHON_REPO_DEBUG_VERBOSITY environment variable.

• (toolchains) The toolchain matching is has been fixed when writingtransitions transitioning on thepython_version flag.Fixes#2685.

• (toolchains) Run the check on the Python interpreter in isolated mode, to ensure it’s not affected by userland environment variables, such asPYTHONPATH.

• (toolchains) Ensure temporary.pyc and.pyo files are also excluded from the interpreters repository files.

• (pypi) Run interpreter version call in isolated mode, to ensure it’s not affected by userland environment variables, such asPYTHONPATH.

• (packaging) An emptyrequires_file is treated as if it were omitted, resulting in a validMETADATA file.

• (rules) py_wheel and sphinxdocs rules now propagatetarget_compatible_with to all targets they create.PR #2788.

• (pypi) Correctly handleMETADATA entries whenpython_full_version is used inthe environment marker.Fixes#2319.

• (pypi) Correctly handlepython_version parameter and transition the requirementlocking to the right interpreter version when usingcompile_pip_requirements rule.See#2819.

Added

• (pypi) From now onsha256 values in therequirements.txt is no longermandatory when enablingpip.parse.experimental_index_url feature.This means thatrules_python will attempt to fetch metadata for allpackages through SimpleAPI unless they are pulled through direct URLreferences. Fixes#2023.In case you see issues withrules_python being too eager to fetch the SimpleAPImetadata, you can use the newly addedpip.parse.simpleapi_skipto skip metadata fetching for those packages.

• (uv) Alock rule that is the replacement for thecompile_pip_requirements. This may still have rough cornersso please report issues with it in the#1975.Main highlights - the locking can be done within a build action or outsideit, there is no more automatictest target (but it can be added on the userside by usingnative_test). For customizing theuv version that is used,please check theuv.configure tag class.

• Add support for riscv64 linux platform.

• (toolchains) Add python 3.13.2 and 3.12.9 toolchains

• (providers) (experimental)PyInfo.site_packages_symlinks field added toallow specifying links to create within the venv site packages (onlyapplicable with--bootstrap_impl=script)(#2156).

• (toolchains) Local Python installs can be used to create a toolchainequivalent to the standard toolchains. See [Local toolchains] docs for how toconfigure them.

• (toolchains) Expose$(PYTHON2_ROOTPATH) and$(PYTHON3_ROOTPATH) which are runfileslocations equivalents of$(PYTHON2) and `$(PYTHON3) respectively.

Removed

• Nothing removed.

Changed

• (deps) platforms 0.0.4 -> 0.0.11

• (py_wheel) Packagepy_library.pyi_srcs (.pyi files) in the wheel.

• (py_package) Packagepy_library.pyi_srcs (.pyi files) inpy_package.

• (gazelle) The generated manifest file (default:gazelle_python.yaml) will now include theYAML document start--- line. Implemented in#2656.

Fixed

• (pypi) Theppc64le is now pointing to the right target in theplatforms package.

• (gazelle) No longer incorrectly mergepy_binary targets during partial updates infile generation mode. Fixed in#2619.

• (bzlmod) Running as root is no longer an error.ignore_root_user_error=Trueis now the default. Note that running as root may still cause spuriousBazel cache invalidation(#1169).

• (gazelle) Don’t collapse depsets to a list or into args when generating the modules mapping file.Support spilling modules mapping args into a params file.

• (coverage) Fix missing files in the coverage report if they have no tests.

• (pypi) From now onpython invocations in repository and module extensionevaluation contexts will invoke Python interpreter with-B to avoidcreating.pyc files.

• (deps) doublestar 4.7.1 (required for recent Gazelle versions)

Added

• (python)python.defaults has been added to allow users toset the default python version in the root module by reading thedefault version number from a file or an environment variable.

• //python/bin:python: convenience target for directly running aninterpreter.--//python/bin:python_src can be used to specify abinary whose interpreter to use.

• (uv) Now the extension can be fully configured viabzlmod APIs without theneed to patchrules_python. The documentation has been added torules_pythondocs but usage of the extension may result in your setup breaking without anynotice. What is more, the URLs and SHA256 values will be retrieved from theGitHub releases page metadata published by theuv project.

• (pypi) An extra argument to add the interpreter lib dir toLDFLAGS whenbuilding wheels fromsdist.

• (pypi) Direct HTTP urls for wheels and sdists are now supported when usingexperimental_index_url (bazel downloader).Partially fixes#2363.

• (rules) APIs for creating custom rules based on the core py_binary, py_test,and py_library rules(#1647)

• (rules) Added env-var to allow additional interpreter args for stage1 bootstrap.SeeRULES_PYTHON_ADDITIONAL_INTERPRETER_ARGS environment variable.Only applicable for--bootstrap_impl=script.

• (rules) Addedinterpreter_args attribute topy_binary andpy_test,which allows pass arguments to the interpreter before the regular args.

• (rules) Addedmain_module attribute topy_binary andpy_test,which allows specifying a module name to run (i.e.python-m<module>).

Removed

• Nothing removed.

Changed

• (rules)py_proto_library is deprecated in favour of theimplementation in https://github.com/protocolbuffers/protobuf. It will beremoved in the future release.

• (pypi)pip.override will now be ignored instead of raising an error,fixes#2550.

• (rules) deprecation warnings for deprecated symbols have been turned off bydefault for now and can be enabled withRULES_PYTHON_DEPRECATION_WARNINGSenv var.

• (pypi) Downgraded versions of packages:pip from24.3.2 to24.0.0 andpackaging from24.2 to24.0.

Fixed

• (rules)python_zip_file output with--bootstrap_impl=script works again(#2596).

• (docs) Usingpython_version attribute for specifying python versions introduced inv1.1.0

• (gazelle) Providing multiple input requirements files togazelle_python_manifest now works correctly.

• (pypi) Handle trailing slashes in pip index URLs in environment variables,fixes#2554.

• (runfiles) Runfile manifest and repository mapping files are now interpretedas UTF-8 on all platforms.

• (coverage) Coverage with--bootstrap_impl=script is fixed(#2572).

• (pypi) Non deterministic behaviour in requirement file usage has been fixedby reverting#2514.The related issue is#908.

• (sphinxdocs) Do not crash whentag_class does not have a populateddoc value.Fixes (#2579).

• (binaries/tests) Fix packaging when using--bootstrap_impl=script: set--venvs_use_declare_symlink=no to have it not create symlinks atbuild time (they will be created at runtime instead).(Fixes#2489)

Added

• Nothing added.

Removed

• Nothing removed.

Changed

• (toolchains) 3.13 means 3.13.1 (previously 3.13.0)

• Bazel 6 support is dropped and Bazel 7.4.1 is the minimum supportedversion, per our Bazel support matrix. Earlier versions are nottested by CI, so functionality cannot be guaranteed.

• (pip.parse) From now we will make fewer calls to indexes whenfetching the metadata from SimpleAPI. The calls will be done in parallel toeach index separately, so the extension evaluation time might slow down ifnot usingpip.parse.experimental_index_url_overrides.

• (pip.parse) Only query SimpleAPI for packages that havesha values in therequirements.txt file.

• (rules) The version-aware rules have been folded into the base rules andthe version-aware rules are now simply aliases for the base rules. Thepython_version attribute is still used to specify the Python version.

• (pypi) Updated versions of packages:pip to 24.3.1 andpackaging to 24.2.

Fixed

• (py_wheel) Use the default shell environment when building wheels to allowtoolchains that search PATH to be used for the wheel builder tool.

• (pypi) The requirement argument parsed towhl_library will now not have envmarker information allowingbazelquery to work in cases where thewhl isavailable for all of the platforms and the sdist can be built. This fix isfor both WORKSPACE andbzlmod setups.Fixes#2450.

• (gazelle) Gazelle will now correctly parse Python3.12 files that usePEP 695 TypeParameter Syntax. (#2396)

• (pypi) Usingpip_parse.experimental_requirement_cycles andpip_parse.use_hub_alias_dependencies together now works whenusing WORKSPACE files.

• (pypi) The error messages when the wheel distributions do not match anythingare now printing more details and include the currently active flagvalues. Fixes#2466.

• (py_proto_library) Fix import paths in Bazel 8.

• (whl_library) Now the changes to the dependencies are correctly tracked whenPyPI packages used inwhl_library during the repository rule phasechange. Fixes#2468.

• (gazelle) Gazelle no longer ignoressetup.py files by default. To restorethis behavior, apply the#gazelle:python_ignore_filessetup.py directive.

• Don’t re-fetch whl_library, python_repository, etc. repository ruleswheneverPATH changes. Fixes#2551.

Added

• (gazelle) Addedinclude_stub_packages flag tomodules_mapping. When set toTrue, thisautomatically includes corresponding stub packages for third-party librariesthat are present and used (e.g.,boto3 →boto3-stubs), improvingtype-checking support.

• (pypi) Freethreaded packages are now fully supported in theexperimental_index_url usage or the regularpip.parse usage.To select the free-threaded interpreter in the repo phase, please usethe documentedenv variables.Fixes#2386.

• (toolchains) Use the latest astral-sh toolchain release20241206 for Python versions:

  • 3.9.21

  • 3.10.16

  • 3.11.11

  • 3.12.8

  • 3.13.1

• (rules) Attributes for type definition files (.pyi files) and type-checkingonly dependencies added. Seepy_library.pyi_srcs andpy_library.pyi_deps (and the same named attributes forpy_binary andpy_test).

• (pypi) pypi-generated targets setpyi_srcs to include*.pyi files.

• (providers)PyInfo has new fields to aid static analysis tools:direct_original_sources,direct_pyi_files,transitive_original_sources,transitive_pyi_files.

Removed

• find_requirements in//python:defs.bzl has been removed.

Changed

Breaking:

• (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.

• (toolchains) consumers who were depending on theMACOS_NAME and thearchattribute in thePLATFORMS list, please update your code to respect the newvalues. The values now correspond to the values available in the@platforms// package constraint values.

• (toolchains)host_platform andinterpreter constants are no longer createdin thetoolchain generated alias.bzl files. If you need to access thehost interpreter during therepository_rule evaluation, please use the@python_{version}_host//:python targets created bypython_register_toolchains andpython_register_multi_toolchains macros or thepythonbzlmod extension.

• (bzlmod)pip.parse.parse_all_requirements_files attribute has been removed.See notes in the previous versions about what to do.

• (deps) rules_cc 0.1.0 (workspace) and 0.0.16 (bzlmod).

• (deps) protobuf 29.0-rc2 (workspace; bzlmod already specifying that version).

Other changes:

• (python_repository) Start honoring thestrip_prefix field forzstd archives.

• (pypi)pip_parse.extra_hub_aliases now works in WORKSPACE files.

• (binaries/tests) For--bootstrap_impl=script, a binary-specific (butotherwise empty) virtual env is used to customizesys.path initialization.

• (deps) bazel_skylib 1.7.0 (workspace; bzlmod already specifying that version)

• (deps) bazel_features 1.21.0; necessary for compatibility with Bazel 8 rc3

• (deps) stardoc 0.7.2 to support Bazel 8.

Fixed

• (toolchains) stop depending onuname to get the value of the host platform.

• (pypi): Correctly handle multiple versions of the same package in the requirementsfiles which is useful when including different PyTorch builds (e.g. <pytorch+cpu> vs <pytorch+cu118> ) for different target platforms.Fixes (2337).

• (uv): Correct the sha256sum for theuv binary for aarch64-apple-darwin.Fixes (2411).

• (binaries/tests) (--bootstrap_impl=scipt) Usingsys.executable willuse the samesys.path setup as the calling binary.(2169).

• (workspace) Corrected protobuf’s name to com_google_protobuf, the name ishardcoded in Bazel, WORKSPACE mode.

• (pypi):compile_pip_requirements no longer fails on Windows when--enable_runfiles is not enabled.

• (pypi):compile_pip_requirements now correctly updates files in the source tree on Windows when--windows_enable_symlinks is not enabled.

• (repositories): Add libs/python3.lib and pythonXY.dll to thelibpython targetdefined by a repository template. This enables stable ABI builds of Python extensionson Windows (by defining Py_LIMITED_API).

• (rules)py_test andpy_binary targets no longer incorrectly remove thefirstsys.path entry when using--bootstrap_impl=script

Added

• (gazelle): Parser failures will now be logged to the terminal. Additionaldetails can be logged by settingRULES_PYTHON_GAZELLE_VERBOSE=1.

• (toolchains) allow users to select which variant of the support host toolchainthey would like to use throughRULES_PYTHON_REPO_TOOLCHAIN_{VERSION}_{OS}_{ARCH} env variable setting. Forexample, this allows one to usefreethreaded python interpreter in therepository_rule to build a wheel fromsdist.

• (toolchain) The python interpreters targetingmuslc libc have been addedfor the latest toolchain versions for each minor Python version. You can controlthe toolchain selection by using the//python/config_settings:py_linux_libc build flag.

• (providers) AddedPyRuntimeInfo.site_init_template andPyRuntimeInfo.site_init_template for specifying the template to use toinitialize the interpreter via venv startup hooks.

• (runfiles) (Bazel 7.4+) Added support for spaces and newlines in runfiles paths

Removed

• (pypi): Removepypi_install_dependencies macro that has been included inpy_repositories for a long time.

• (bzlmod): RemoveDEFAULT_PYTHON_VERSION frominterpreters.bzl file. Ifyou need the version, please use it from theversions.bzl file instead.

Changed

• Nothing changed.

Fixed

• (rules) Don’t drop custom import paths if Bazel-builtin PyInfo is removed.(2414).

Added

• Nothing added.

Removed

• (publish) Remove deprecatedrequirements.txt for thetwine dependencies.Please userequirements_linux.txt instead.

• (python_repository) Use bazel’s built inzstd support and remove attributesfor customizing thezstd binary to be used forzstd archives in thepython_repository repository_rule. This affects thepython_register_toolchains andpython_register_multi_toolchains callers in theWORKSPACE.

Changed

• (deps) bazel_skylib 1.6.1 -> 1.7.1

• (deps) rules_cc 0.0.9 -> 0.0.14

• (deps) protobuf 24.4 -> 29.0-rc2

• (deps) rules_proto 6.0.0-rc1 -> 6.0.2

• (deps) stardoc 0.6.2 -> 0.7.1

• For bzlmod, Bazel 7.4 is now the minimum Bazel version.

• (toolchains) Use the latest indygreg toolchain release20241016 for Python versions:

  • 3.9.20

  • 3.10.15

  • 3.11.10

  • 3.12.7

  • 3.13.0

• (pypi) The naming scheme for thebzlmod spoke repositories have changed asall of the givenrequirements.txt files are now parsed bydefault, totemporarily restore the behavior, you can usepip.parse.extra_hub_aliases, which will be removed or made noop inthe future.

Fixed

• (precompiling) Skip precompiling (instead of erroring) if the legacy@bazel_tools//tools/python:autodetecting_toolchain is being used(#2364).

Added

• Bazel 8 is now supported.

• (toolchain) Support for freethreaded Python toolchains is now available. Usethe config flag//python/config_settings:py_freethreaded to toggle theselection of the free-threaded toolchains.

• (toolchain)py_runtime.abi_flags attribute andPyRuntimeInfo.abi_flags field added.

Removed

• Support for Bazel 6 using bzlmod has been dropped.

Changed

• (deps) (WORKSPACE only) rules_cc 0.0.13 and protobuf 27.0 is now the defaultversion used; this for Bazel 8+ support (previously version was rules_cc 0.0.9and no protobuf version specified)(2310).

• (publish) The dependencies have been updated to the latest available versionsfor thetwine publishing rule.

• (whl_library) Remove--no-build-isolation to allow non-hermetic sdist buildsby default. Users wishing to keep this argument and to enforce more hermeticbuilds can do so by passing the argument inpip.parse#extra_pip_args

• (pip.parse)pip.parse.whl_modifications now normalizes the given whl namesand nowpyyaml andPyYAML will both work.

• (bzlmod)pip.parse spoke repository naming will be changed in an upcomingrelease in places where the users specify different package versions perplatform in the same hub repository. The naming of the spoke repos isconsidered an implementation detail and we advise the users to use thehubrepository directly and make use ofpip.parse.extra_hub_aliasesfeature added in this release.

Fixed

• (pypi) (Bazel 7.4+) Allow spaces in filenames included inwhl_librarys(617).

• (pypi) Whenpip.parse.experimental_index_url is set, we need to stillpass theextra_pip_args value when building ansdist.

• (pypi) The patched wheel filenames from now on are using local version specifierswhich fixes usage of the said wheels using standard package managers.

• (bzlmod) The extension evaluation has been adjusted to always generate thesame lock file irrespective ifexperimental_index_url is set by any moduleor not. To opt into this behavior, setpip.parse.parse_all_requirements_files, which will become thedefault in future releases leading up to1.0.0. Fixes#2268. A knownissue is that it may breakbazelquery and in these use cases it isadvisable to usecquery or switch todownload_only=True

Added

• (publish) The requirements file for thetwine publishing rules have beenupdated to have a new convention:requirements_darwin.txt,requirements_linux.txt,requirements_windows.txt for each respective OSand one extra filerequirements_universal.txt if you prefer a single file.Therequirements.txt file may be removed in the future.

• The rules_python version is now reported in//python/features.bzl#features.version

• (pip.parse)pip.parse.extra_hub_aliases can now be used to expose extratargets created by annotations in whl repositories.Fixes#2187.

• (bzlmod)pip.parse now supportswhl-only setup usingdownload_only=True where users can specify multiple requirements filesand use thepip backend to do the downloading. This was only available forusers settingpip.parse.experimental_index_url, but now users havemore options whilst we continue to work on stabilizing the experimental feature.

Fixed

• (bzlmod) Generateconfig_setting values for all available toolchains insteadof only the registered toolchains, which restores the previous behaviour thatbzlmod users would have observed.

Fixed

• (rules) Setting--incompatible_python_disallow_native_rules no longercauses rules_python rules to fail(#2326).

Changed

• BREAKINGpy_library no longer puts its source files or generated pycfiles in runfiles; it’s the responsibility of consumers (e.g. binaries) topopulate runfiles with the necessary files. Adding source files to runfilescan be temporarily restored by setting--add_srcs_to_runfiles=enabled,but this flag will be removed in a subsequent releases.

• PyInfo.transitive_sources is now added to runfiles. These files are.py files that are required to be added to runfiles by downstream binaries(or equivalent).

• (toolchains)py_runtime.implementation_name now defaults tocpython(previously it defaulted to None).

• (toolchains) The exec tools toolchain is enabled by default. It can bedisabled by setting--@rules_python//python/config_settings:exec_tools_toolchain=disabled.

• (deps) stardoc 0.6.2 added as dependency.

Fixed

• (bzlmod) Thepython.override(minor_mapping) now merges the default and theoverridden versions ensuring that the resultantminor_mapping will alwayshave all of the python versions.

• (bzlmod) The default value for the--python_version flag will now bealways set to the default python toolchain version value.

• (bzlmod) correctly wire thepip.parse.extra_pip_args all theway towhl_library. What is more we will pass theextra_pip_args towhl_library forsdist distributions when usingpip.parse.experimental_index_url. See#2239.

• (whl_filegroup): Provide per default also theRECORD file

• (py_wheel):RECORD file entry elements are now quoted if necessary when awheel is created

• (whl_library) truncate progress messages from the repo rule to better handlecase where a requirement has many--hash=sha256:... flags

• (rules)compile_pip_requirements passesenv to theX.update target (andnot only to theX_test target, a bug introduced in#1067).

• (bzlmod) In hybrid bzlmod with WORKSPACE builds,python_register_toolchains(register_toolchains=True) is respected(#1675).

• (precompiling) Thepyc_collection attribute now correctlyenables (or disables) using pyc files from targets transitively

• (pip) Skip patching wheels not matchingpip.override’sfile(#2294).

• (chore): Add arules_shell dev dependency and moved ash_test targetoutside of the//:BUILD.bazel file.Fixes#2299.

Added

• (py_wheel) Now supportscompress=(True|False) to allow disablingcompression to speed up development.

• (toolchains): A public//python/config_settings:python_version_major_minor hasbeen exposed for users to be able to match on theX.Y version of a Pythoninterpreter.

• (api) Addedmerge_py_infos() so user rules can merge and propagatePyInfo without losing information.

• (toolchains) New Python versions available: 3.13.0 using the20241008 release.

• (toolchains): Bump default toolchain versions to:

  • 3.8->3.8.20

  • 3.9->3.9.20

  • 3.10->3.10.15

  • 3.11->3.11.10

  • 3.12->3.12.7

• (coverage) Add support for python 3.13 and bumpcoverage.py to 7.6.1.

• (bzlmod) Add support fordownload_only flag to disable usage ofsdistswhenpip.parse.experimental_index_url is set.

• (api) PyInfo fields:PyInfo.transitive_implicit_pyc_files,PyInfo.transitive_implicit_pyc_source_files.

Removed

• (precompiling)--precompile_add_to_runfiles has been removed.

• (precompiling)--pyc_collection has been removed. Thepyc_collectionattribute now bases its default on--precompile.

• (precompiling) Theprecompile=if_generated_source value has been removed.

• (precompiling) Theprecompile_source_retention=omit_if_generated_source value has been removed.

Changed

• (gazelle): Update error messages when unable to resolve a dependency to be more human-friendly.

• (flags) The--python_version flag now also returnsconfig_common.FeatureFlagInfo.

• (toolchain): The toolchain patches now expose thepatch_strip attributethat one should use when patching toolchains. Please set it if you arepatching python interpreter. In the next release the default will be set to0 which better reflects the defaults used in publicbazel APIs.

• (toolchains) Whenpy_runtime.interpreter_version_info isn’t specified,the--python_version flag will determine the value. This allowsspecifying the build-time Python version for theruntime_env_toolchains.

• (toolchains)py_cc_toolchain.libs andPyCcToolchainInfo.libs isoptional. This is to support situations where only the Python headers areavailable.

• (bazel) Minimum bazel 7 version that we test against has been bumped to7.1.

Fixed

• (whl_library): Remove--no-index and add--no-build-isolation to thepipinstall command when installing a wheel from a local file, which happenswhenexperimental_index_url flag is used.

• (bzlmod) get the path to the host python interpreter in a way that results inplatform non-dependent hashes in the lock file when the requirement markers needto be evaluated.

• (bzlmod) correctly watch sources used for evaluating requirement markers forany changes so that the repository rule or module extensions can bere-evaluated when the said files change.

• (gazelle): Fix incorrect use oft.Fatal/t.Fatalf in tests.

• (toolchain) Omit third-party python packages from coverage reports fromstage2 bootstrap template.

• (bzlmod) Properly handle relative path URLs in parse_simpleapi_html.bzl

• (gazelle) Correctly resolve deps that have top-level module overlap with a gazelle_python.yaml dep module

• (rules) MakeRUNFILES_MANIFEST_FILE-based invocations work when used with--bootstrap_impl=script. This fixes invocations using non-sandboxedtest execution with--enable_runfiles=false--build_runfile_manifests=true.(#2186).

• (py_wheel) Fix incorrectly generatedRequired-Dist when specifying requirements with markersin extra_requires in py_wheel rule.

• (rules) Prevent pytest from trying run the generated stage2bootstrap .py file when using--bootstrap_impl=script

• (toolchain) Thegen_python_config_settings has been fixed to includethe flag_values from the platform definitions.

Added

• (bzlmod): Toolchain overrides can now be done using the newpython.override,python.single_version_override andpython.single_version_platform_override tag classes.See#2081.

• (rules) Executables providePyExecutableInfo, which containsexecutable-specific information useful for packaging an executable oror deriving a new one from the original.

• (py_wheel) Removed use of bash to avoid failures on Windows machines which do nothave it installed.

• (docs) Automatically generated documentation forpython_register_toolchainsand related symbols.

• (toolchains) Addedpython_repository.patch_strip attribute forallowing values that are other than1, which has been hard-coded up untilnow. If you are relying on the undocumentedpatches support inTOOL_VERSIONS for registering patched toolchains please consider settingthepatch_strip explicitly to1 if you depend on this value - in thefuture the value may change to default to0.

• (toolchains) Added//python:none, a special target for use withpy_exec_tools_toolchain.exec_interpreter to treat the value asNone.

Removed

• (toolchains): Removed accidentally exposedhttp_archive symbol frompython/repositories.bzl.

• (toolchains): An internalis_python_config_setting macro has been removed.

Changed

• (whl_library) A better log message when the wheel is built from an sdist orwhen the wheel is downloaded usingdownload_only feature to aid debugging.

• (gazelle): Simplify and make gazelle_python.yaml have only top level package name.It would work well in cases to reduce merge conflicts.

• (toolchains): Change some old toochain versions to use20240726 release toinclude dependency updates3.8.19,3.9.19,3.10.14,3.11.9

• (toolchains): Bump default toolchain versions to:

  • 3.12->3.12.4

• (rules)PYTHONSAFEPATH is inherited from the calling environment to allowdisabling it (Requires--bootstrap_impl=script)(#2060).

Fixed

• (rules)compile_pip_requirements now sets theUSERPROFILE env variable onWindows to work around an issue wheresetuptools fails to locate the user’shome directory.

• (rules) correctly handle absolute URLs in parse_simpleapi_html.bzl.

• (rules) Fixes build targets linking against@rules_python//python/cc:current_py_cc_libsin host platform builds on macOS, by editing theLC_ID_DYLIB field of the hermetic interpreter’slibpython3.x.dylib usinginstall_name_tool, setting it to its absolute path under Bazel’sexecroot.

• (rules) Signals are properly received when using--bootstrap_impl=script(for non-zip builds).(#2043)

• (rules) Fixes Python builds when the--build_python_zip is set tofalse onWindows. See#1840.

• (rules) Fixes Mac +--build_python_zip +--bootstrap_impl=script(#2030).

• (rules) User dependencies come before runtime site-packages when using--bootstrap_impl=script.(#2064).

• (rules) Version-aware rules now return both@_builtins and@rules_pythonproviders instead of only one.(#2114).

• (pip) Fixed pypi parse_simpleapi_html function for feeds with package metadatacontaining “>” sign

• (toolchains) Added missing executable permission to//python/runtime_env_toolchains interpreter script so that it is runnable.(#2085).

• (pip) Correctly use thesdist downloaded by the bazel downloader when usingexperimental_index_url feature. Fixes#2091.

• (gazelle) Makegazelle_python_manifest.update manual to avoid unnecessarynetwork behavior.

• (bzlmod): The conflicting toolchains duringpython extension will no longercause warnings by default. In order to see the warnings for diagnostic purposesset the env varRULES_PYTHON_REPO_DEBUG_VERBOSITY to one ofINFO,DEBUG orTRACE.Fixes#1818.

• (runfiles) Make runfiles lookups work for the situation of Bazel 7,Python 3.9 (or earlier, where safepath isn’t present), and the Rlocation callin the same directory as the main file.Fixes#1631.

Added

• (rules)compile_pip_requirements supports multiple requirements input files assrcs.

• (rules)PYTHONSAFEPATH is inherited from the calling environment to allowdisabling it (Requires--bootstrap_impl=script)(#2060).

• (gazelle) Addedpython_generation_mode_per_package_require_test_entry_pointin order to better accommodate users who use a custom macro,pytest-bazel,rules_python_pytest orrules_pypy_test_main in order to integrate withpytest. Currently the defaultflag value is set totrue for backwards compatible behaviour, but in thefuture the flag will be flipped befalse by default.

• (toolchains) New Python versions available:3.12.4 using the20240726 release.

• (pypi) Support env markers in requirements files. Note, that this means thatif your requirements files contain env markers, the Python interpreter willneed to be run during bzlmod phase to evaluate them. This may incurdownloading an interpreter (for hermetic-based builds) or cause non-hermeticbehavior (if using a system Python).

Changed

• protobuf/com_google_protobuf dependency bumped tov24.4

• (bzlmod): optimize the creation of config settings used in pip toreduce the total number of targets in the hub repo.

• (toolchains) The exec tools toolchain now finds its interpreter by reusingthe regular interpreter toolchain. This avoids having to duplicate specifyingwhere the runtime for the exec tools toolchain is.

• (toolchains) (//python:autodetecting_toolchain) is deprecated. It isreplaced by//python/runtime_env_toolchains:all. The old target will beremoved in a future release.

Fixed

• (bzlmod): When usingexperimental_index_url theall_requirements,all_whl_requirements andall_data_requirements will now only includecommon packages that are available on all target platforms. This is to ensurethat packages that are only present for some platforms are pulled only viathedeps of the materializedpy_library. If you would like to includeplatform specific packages, using aselect statement with references to thespecific package will still work (e.g.

  my_attr=all_requirements+select({"@platforms//os:linux":["@pypi//foo_available_only_on_linux"],"//conditions:default":[],})

• (bzlmod): Targets inall_requirements now use the same form as targets returned by therequirement macro.

• (rules) Auto exec groups are enabled. This allows actions run by the rules,such as precompiling, to pick an execution platform separately from whatother toolchains support.

• (providers)PyRuntimeInfo doesn’t require passing theinterpreter_version_info arg.

• (bzlmod) Correctly passisolated,quiet andtimeout values towhl_libraryand drop the defaults from the lock file.

• (whl_library) Correctly handle arch-specific dependencies when we encounter aplatform specific wheel and useexperimental_target_platforms.Fixes#1996.

• (rules) The first element of the default outputs is now the executable again.

• (pip) Fixed crash when pypi packages lacked a sha (e.g. yanked packages)

Added

• (toolchains)//python/runtime_env_toolchains:all, which is a drop-inreplacement for the “autodetecting” toolchain.

• (gazelle) Added newpython_label_convention andpython_label_normalization directives. These directiveallows altering default Gazelle label format to third-party dependencies useful for re-using Gazelle pluginwith other rules, includingrules_pycross. See#1939.

Removed

• (pip): Removes theentrypoint macro that was replaced bypy_console_script_binary in 0.26.0.

Fixed

• (toolchains) Theexec_tools_toolchain_type is disabled by default.To enable it, set--//python/config_settings:exec_tools_toolchain=enabled.This toolchain must be enabled for precompilation to work. This toolchain willbe enabled by default in a future release.Fixes#1967.

Fixed

• (py_binary) Fix building of zip file when using--build_python_zipargument. Fixes#1954.

Changed

• (deps) Upgrade thepip_install dependencies to pick up a new version of pip.

• (toolchains) Optional toolchain dependency:py_binary,py_test, andpy_library now depend on the//python:exec_tools_toolchain_type for buildtools.

• (deps): Bumpedbazel_skylib to 1.6.1.

• (bzlmod): Thepython and internalrules_python extensions have beenmarked asreproducible and will not include any lock file entries from nowon.

• (gazelle): Remove gazelle plugin’s python deps and make it hermetic.Introduced a new Go-based helper leveraging tree-sitter for syntax analysis.Implemented the use ofpypi/stdlib-list for standard library module verification.

• (pip.parse): Do not ignore yanked packages when usingexperimental_index_url.This is to mimic whatuv is doing. We will print a warning instead.

• (pip.parse): Add references to all supported wheels when usingexperimental_index_urlto allowing to correctly fetch the wheels for the right platform. See theupdated docs on how to use the feature. This is work towards addressing#735 and#260. The spokerepository names when using this flag will have a structure of{pip_hub_prefix}_{wheel_name}_{py_tag}_{abi_tag}_{platform_tag}_{sha256},which is an implementation detail which should not be relied on and is therepurely for better debugging experience.

• (bzlmod) Thepythons_hub//:interpreters.bzl no longer has platform-specificlabels which where left there for compatibility reasons. Move topython_{version}_host keys if you would like to have access to a Pythoninterpreter that can be used in a repository rule context.

Fixed

• (gazelle) Removevisibility fromNonEmptyAttr.Now empty(have nodeps/main/srcs/imports attr)py_library/test/binary rules willbe automatically deleted correctly. For example, ifpython_generation_modeis set to package, when__init__.py is deleted, thepy_library generatedfor this package before will be deleted automatically.

• (whl_library): Useis_python_config_setting to correctly handle multi-pythonversion dependency select statements when theexperimental_target_platformsincludes the Python ABI. The default python version case within the select isalso now handled correctly, stabilizing the implementation.

• (gazelle) Fix Gazelle failing on Windows with“panic: runtime error: invalid memory address or nil pointer dereference”

• (bzlmod) removepip.parse(annotations) attribute as it is unused and has beenreplaced by whl_modifications.

• (pip) Correctly select wheels when the python tag includes minor versions.See (#1930)

• (pip.parse): The lock file is now reproducible on any host platform if theexperimental_index_url is not used by any of the modules in the dependencychain. To make the lock file identical on eachos andarch, please usetheexperimental_index_url feature which will fetch metadata from PyPI or adifferent private index and write the contents to the lock file. Fixes#1643.

• (pip.parse): Installyanked packages and print a warning instead ofignoring them. This better matches the behaviour ofuvpipinstall.

• (toolchains): Now matching of the default hermetic toolchain is more robustand explicit and should fix rare edge-cases where the host toolchainautodetection would match a different toolchain than expected. This may yieldto toolchain selection failures when the python toolchain is not registered,but is requested via//python/config_settings:python_version flag setting.

• (doc) Fix theWORKSPACE requirement vendoring example. Fixes#1918.

Added

• (rules) Precompiling Python source at build time is available. but isdisabled by default, for now. Set@rules_python//python/config_settings:precompile=enabled to enable itby default. A subsequent release will enable it by default. See thePrecompiling docs and API reference docs for moreinformation on precompiling. Note this requires Bazel 7+ and the Pystar ruleimplementation enabled.(#1761)

• (rules) Attributes and flags to control precompile behavior:precompile,precompile_optimize_level,precompile_source_retention,precompile_invalidation_mode, andpyc_collection

• (toolchains) The target runtime toolchain (//python:toolchain_type) hastwo new optional attributes:pyc_tag (tells the pyc filename infix to use) andimplementation_name (tells the Python implementation name).

• (toolchains) A toolchain type for build tools has been added://python:exec_tools_toolchain_type.

• (providers)PyInfo has two new attributes:direct_pyc_files andtransitive_pyc_files, which tell the pyc files a target makes availabledirectly and transitively, respectively.

• //python:features.bzl added to allow easy feature-detection in the future.

• (pip) Allow specifying the requirements by (os, arch) and add extravalidations when parsing the inputs. This is a non-breaking change for mostusers unless they have been passing multiplerequirements_* files togetherwithextra_pip_args=["--platform=manylinux_2_4_x86_64"], that was aninvalid usage previously but we were not failing the build. From now on thisis explicitly disallowed.

• (toolchains) Added riscv64 platform definition for python toolchains.

• (gazelle) Thepython_visibility directive now supports the$python_root$placeholder, just like thepython_default_visibility directive does.

• (rules) A new bootstrap implementation that doesn’t require a system Pythonis available. It can be enabled by setting--@rules_python//python/config_settings:bootstrap_impl=script. Itwill become the default in a subsequent release.(#691)

• (providers)PyRuntimeInfo has two new attributes:PyRuntimeInfo.stage2_bootstrap_template andPyRuntimeInfo.zip_main_template.

• (toolchains) A replacement for the Bazel-builtn autodetecting toolchain isavailable. The//python:autodetecting_toolchain alias now uses it.

• (pip): Support fetching and using the wheels for other platforms. Thissupports customizing whether the linux wheels are pulled formusl orglibc, whetheruniversal2 or arch-specific MacOS wheels are preferred andit also allows to select a particularlibc version. All of this is done viathestring_flags in@rules_python//python/config_settings. If there areno wheels that are supported for the target platform,rules_python willfallback onto building thesdist from source. This behaviour can bedisabled if desired using one of the available string flags as well.

• (whl_filegroup) Added a newwhl_filegroup rule to extract files from a wheel file.This is useful to extract headers for use in acc_library.

Fixed

• Workaround existence of infinite symlink loops on case insensitive filesystems when targeting linux platforms with recent Python toolchains. Works around an upstreamissue. Fixes#1800.

Changed

• (bzlmod): TheMODULE.bazel.lockwhl_library rule attributes are nowsorted in the attributes section. We are also removing values that are notdefault in order to reduce the size of the lock file.

• (coverage) Bumpcoverage.py to7.4.3.

• (deps): Bumpedbazel_features to 1.9.1 to detect optional supportnon-blocking downloads.

• (deps): Updatedpip_tools to >= 7.4.0

• (toolchains): Change some old toolchain versions to use20240224 release toinclude security fixes3.8.18,3.9.18 and3.10.13

• (toolchains): Bump default toolchain versions to:

  • 3.8->3.8.19

  • 3.9->3.9.19

  • 3.10->3.10.14

  • 3.11->3.11.9

  • 3.12->3.12.3

Fixed

• (whl_library): Fix the experimental_target_platforms overriding for platformspecific wheels when the wheels are for any python interpreter version. Fixes#1810.

• (whl_library): Stop generating duplicate dependencies when encounteringduplicates in the METADATA. Fixes#1873.

• (gazelle) Inproject orpackage generation modes, do not generatepy_testrules when there are no test files and do not setmain="__test__.py" whenthat file doesn’t exist.

• (whl_library) The group redirection is only added when the package is part ofthe group potentially fixing aspects that want to traverse apy_library graph.Fixes#1760.

• (bzlmod) Setting a particular micro version for the interpreter and thepip.parse extension is now possible, see theexamples/pip_parse/MODULE.bazel for how to do it.See#1371.

• (refactor) The pre-commit developer workflow should now passisort andblackchecks (see#1674).

Added

• (toolchains) Added armv7 platform definition for python toolchains.

• (toolchains) New Python versions available:3.11.8,3.12.2 using the20240224 release.

• (toolchains) New Python versions available:3.8.19,3.9.19,3.10.14,3.11.9,3.12.3 usingthe20240415 release.

• (gazelle) Added a newpython_visibility directive to control visibilityof generated targets by appending additional visibility labels.

• (gazelle) Added a newpython_default_visibility directive to control thedefault visibility of generated targets. See thedocsfor details.

• (gazelle) Added a newpython_test_file_pattern directive. This directive tellsgazelle which python files should be mapped to thepy_test rule. See theoriginal issue and thedocsfor details.

• (wheel) Add support fordata_files attributes in py_wheel rule(#1777)

• (py_wheel)bzlmod installations now provide atwine setup for the defaultPython toolchain inrules_python for version 3.11.

• (bzlmod) Newexperimental_index_url,experimental_extra_index_urls andexperimental_index_url_overrides topip.parse for using the bazeldownloader. If you see any issues, report in#1357. The URLs forthe whl and sdist files will be written to the lock file. Controlling whetherthe downloading of metadata is done in parallel can be done usingparallel_download attribute.

• (gazelle) Add a new annotationinclude_dep. Also add documentation forannotations togazelle/README.md.

• (deps):rules_python depends now onrules_cc 0.0.9

• (pip_parse): A new flaguse_hub_alias_dependencies has been added that is goingto become default in the next release. This makes use ofdep_template flagin thewhl_library rule. This also affects theexperimental_requirement_cycles feature where the dependencies that are ina group would be only accessible via the hub repo aliases. If you stilldepend on legacy labels instead of the hub repo aliases and you use theexperimental_requirement_cycles, now is a good time to migrate.

Changed

• For Bazel 7, the core rules and providers are now implemented in rules_pythondirectly and the rules bundled with Bazel are not used. Bazel 6 and earliercontinue to use the Bazel builtin symbols. Of particular note, this means,under Bazel 7, the builtin global symbolPyInfo isnot the same as whatis loaded from rules_python. The same is true ofPyRuntimeInfo.

Changed

• (toolchains) Windows hosts always ignore pyc files in the downloaded runtimes.This fixes issues due to pyc files being created at runtime and affecting thedefinition of what files were considered part of the runtime.

• (pip_parse) Added theenvsubst parameter, which enables environment variablesubstitutions in theextra_pip_args attribute.

• (pip_repository) Added theenvsubst parameter, which enables environmentvariable substitutions in theextra_pip_args attribute.

Fixed

• (bzlmod) pip.parse now does not fail with an emptyrequirements.txt.

• (py_wheel) Wheels generated bypy_wheel now preserve executable bits whenbeing extracted byinstaller and/orpip.

• (coverage) During the running of lcov, the stdout/stderr was causing testfailures. By default, suppress output when generating lcov. This can beoverridden by setting ‘VERBOSE_COVERAGE’. This change only affect bazel7.x.x and above.

• (toolchain) Changed thehost_toolchain to symlink all files to supportWindows host environments without symlink support.

• (PyRuntimeInfo) Switch back to builtin PyRuntimeInfo for Bazel 6.4 and whenpystar is disabled. This fixes an error abouttarget...doesnothave...PyRuntimeInfo.(#1732)

Added

• (py_wheel) Addedrequires_file andextra_requires_files attributes.

• (whl_library)experimental_target_platforms now supports specifying thePython version explicitly and the outputBUILD.bazel file will be correctirrespective of the python interpreter that is generating the file andextracting thewhl distribution. Multiple python target version can bespecified and the code generation will generate version specific dependencyclosures but that is not yet ready to be used and may break the build ifthe default python version is not selected usingcommon--@rules_python//python/config_settings:python_version=X.Y.Z.

• New Python versions available:3.11.7,3.12.1 usinghttps://github.com/indygreg/python-build-standalone/releases/tag/20240107.

• (toolchain) Allow settingx.y as thepython_version parameter inthe version-awarepy_binary andpy_test rules. This allows users touse the same rule import for testing with specific Python versions andrely on toolchain configuration and how the latest version takes precedenceif e.g.3.8 is selected. That also simplifies.bazelrc for any usersthat set the defaultpython_version string flag in that way.

• (toolchain) The runtime’s shared libraries (libpython.so et al) can beaccessed using@rules_python//python/cc:current_py_cc_libs. This usestoolchain resolution, so the files are from the same runtime used to run atarget. If you were previously using e.g.@python_3_11//:libpython, thenswitch to:current_py_cc_libs for looser coupling to the underlying runtimerepo implementation.

• (repo rules) The environment variableRULES_PYTHON_REPO_DEBUG=1 can beset to make repository rules log detailed information about what they’reup to.

• (coverage) Add support for python 3.12 and bumpcoverage.py to7.4.1.

Changed

• BREAKING The deprecatedincompatible_generate_aliases feature flagsfrompip_parse andgazelle got removed. They had been flipped toTruein 0.27.0 release.

• BREAKING (wheel) Theincompatible_normalize_name andincompatible_normalize_version flags have been removed. They had beenflipped toTrue in 0.27.0 release.

• (bzlmod) The pip hub repository now uses the newly introduced config settingsusing theX.Y python version notation. This improves cross moduleinteroperability and allows to share wheels built by interpreters usingdifferent patch versions.

Fixed

• (bzlmod pip.parse) Use a platform-independent reference to the interpreterpip uses. This reduces (but doesn’t eliminate) the amount ofplatform-specific content inMODULE.bazel.lock files; Follow#1643 for removingplatform-specific content inMODULE.bazel.lock files.

• (wheel) The stamp variables inside the distribution name are no longerlower-cased when normalizing under PEP440 conventions.

Added

• (toolchains)python_register_toolchains now also generates a repositorythat is suffixed with_host, that has a single label:python that is asymlink to the python interpreter for the host platform. The intended use ismainly inrepository_rule, which are always run usinghost platformPython. This means thatWORKSPACE users can now copy therequirements.bzlfile for vendoring as seen in the updatedpip_parse_vendored example.

• (runfiles)rules_python.python.runfiles.Runfiles now has a staticCreatemethod to make imports more ergonomic. Users should only need to import theRunfiles object to locate runfiles.

• (toolchains)PyRuntimeInfo now includes ainterpreter_version_info fieldthat contains the static version information for the given interpreter.This can be set viapy_runtime when registering an interpreter toolchain,and will done automatically for the builtin interpreter versions registered viapython_register_toolchains.Note that this only available on the Starlark implementation of the provider.

• (config_settings) Added//python/config_settings:is_python_X.Y configsettings to match on minor Python version. These settings match anyX.Yversion instead of just an exactX.Y.Z version.

Changed

• BREAKING (pip_install) the deprecatedpip_install macro and relateditems have been removed.

• BREAKING Support for Bazel 5 has been officially dropped. This releasewas only partially tested with Bazel 5 and may or may not work with Bazel 5.Subsequent versions will no longer be tested under Bazel 5.

• (runfiles)rules_python.python.runfiles now directly implements type hintsand drops support for python2 as a result.

• (toolchains)py_runtime,py_runtime_pair, andPyRuntimeInfo now use therules_python Starlark implementation, not the one built into Bazel. NOTE: Thisonly applies to Bazel 6+; Bazel 5 still uses the builtin implementation.

• (pip_parse) The parameterexperimental_requirement_cycles may be provided amap of names to lists of requirements which form a dependencycycle.pip_parse will break the cycle for you transparently. This behavioris also available under bzlmod aspip.parse(experimental_requirement_cycles={}).

• (toolchains)py_runtime can now take an executable target. Note: runfilesfrom the target are not supported yet.(#1612)

• (gazelle) Whenpython_generation_mode is set tofile, create onepy_binarytarget for each file withif__name__=="__main__" instead of just onepy_binary for the whole module.

• (gazelle) the Gazelle manifest integrity field is now optional. If therequirements argument togazelle_python_manifest is unset, no integrityfield will be generated.

Fixed

• (gazelle) The gazelle plugin helper was not working with Python toolchains 3.11and above due to a bug in the helper components not being on PYTHONPATH.

• (pip_parse) The repositories created bywhl_library can now parse thewhlMETADATA and generate dependency closures irrespective of the host platformthe generation is executed on. This can be turned on by supplyingexperimental_target_platforms=["all"] to thepip_parse or thebzlmodequivalent. This may help in cases where fetching wheels for a differentplatform usingdownload_only=True feature.

• (bzlmod pip.parse) Thepip.parse(python_interpreter) arg now works forspecifying a local system interpreter.

• (bzlmod pip.parse) Requirements files with duplicate entries for the samepackage (e.g. one for the package, one for an extra) now work.

• (bzlmod python.toolchain) Submodules can now (re)register the Python versionthat rules_python has set as the default.(#1638)

• (whl_library) Actually use the provided patches to patch the whl_library.On Windows the patching may result in files with CRLF line endings, as a resultthe RECORD file consistency requirement is lifted and now a warning is emittedinstead with a location to the patch that could be used to silence the warning.Copy the patch to your workspace and add it to the list if patches for the wheelfile if you decide to do so.

• (coverage): coverage reports are now created when the version-awarerules are used.(#1600)

• (toolchains) Workspace builds register the py cc toolchain (bzlmod alreadywas). This makes e.g.//python/cc:current_py_cc_headers Just Work.(#1669)

• (bzlmod python.toolchain) The value ofignore_root_user_error is now decidedby the root module only.(#1658)

Added

• (docs) bzlmod extensions are now documented on rules-python.readthedocs.io

• (docs) Support and backwards compatibility policies have been documented.See https://rules-python.readthedocs.io/en/latest/support.html

• (gazelle)file generation mode can now also add__init__.py to the srcsattribute for every target in the package. This is enabled through a separatedirectivepython_generation_mode_per_file_include_init.

Changed

• Make//python/pip_install:pip_repository_bzlbzl_library target internalas all of the publicly available symbols (etc.package_annotation) arere-exported via//python:pip_bzlbzl_library.

• (gazelle) Gazelle Python extension no longer has runtime dependencies. UsingGAZELLE_PYTHON_RUNTIME_DEPS from@rules_python_gazelle_plugin//:def.bzl isno longer necessary.

• (pip_parse) The installation ofpip_parse repository rule toolchaindependencies is now done as part ofpy_repositories call.

• (pip_parse) The generatedrequirements.bzl file now has an additional symbolall_whl_requirements_by_package which provides a map from the normalizedPyPI package name to the target that provides the built wheel file. Usepip_utils.normalize_name function from@rules_python//python:pip.bzl toconvert a PyPI package name to a key in theall_whl_requirements_by_packagemap.

• (pip_parse) The flagincompatible_generate_aliases has been flipped toTrue by default onnon-bzlmod setups allowing users to use the same labelstrings during the transition period. For example, instead of@pypi_foo//:pkg, you can now use@pypi//foo or@pypi//foo:pkg. Otherlabels that are present in thefoo package aredist_info,whl anddata. Note, that the@pypi_foo//:pkg labels are still present forbackwards compatibility.

• (gazelle) The flaguse_pip_repository_aliases is now set toTrue bydefault, which will causegazelle to change third-party dependency labelsfrom@pip_foo//:pkg to@pip//foo by default.

• Thecompile_pip_requirements now defaults topyproject.toml if thesrcorrequirements_in attributes are unspecified, matching the upstreampip-compile behaviour more closely.

• (gazelle) Use relative paths if possible for dependencies added throughthe use of theresolve directive.

• (gazelle) When usingpython_generation_modefile, onepy_test target ismade per test file even if a target named__test__ or a file named__test__.py exists in the same package. Previously in these cases therewould only be one test target made.

Breaking changes:

• (pip)pip_install repository rule in this release has been disabled andwill fail by default. The API symbol is going to be removed in the nextversion, please migrate topip_parse as a replacement. Thepip_parserule no longer supportsrequirements attribute, please userequirements_lock instead.

• (py_wheel) switchincompatible_normalize_name andincompatible_normalize_version toTrue by default to enforcePEP440for wheel names built byrules_python.

• (tools/wheelmaker.py) drop support for Python 2 as only Python 3 is tested.

Fixed

• Skip aliases for unloaded toolchains. Some Python versions that don’t have fullplatform support, and referencing their undefined repositories can break operationslikebazelqueryrdeps(...).

• Python code generated fromproto_library withstrip_import_prefix can be imported now.

• (py_wheel) Produce deterministic wheel files and makeRECORD file entriesfollow the order of files written to the.whl archive.

• (gazelle) Generate a singlepy_test target whengazelle:python_generation_modeprojectis used.

• (gazelle) Move waiting for the Python interpreter process to exit to the shutdown hookto make the usage of theexec.Command more idiomatic.

• (toolchains) Keep tcl subdirectory in Windows build of hermetic interpreter.

• (bzlmod) sub-modules now don’t have the//conditions:default clause in thehub repos created bypip.parse. This should fix confusing error messagesin case there is a misconfiguration of toolchains or a bug inrules_python.

Added

• (bzlmod) Added.whl patching support viapatches andpatch_striparguments to the newpip.override tag class.

• (pip) Support for usingPEP621 compliantpyproject.toml for creating a resolvedrequirements.txt file.

• (utils) Added apip_utils struct with anormalize_name function to allow usersto find out howrules_python would normalize a PyPI distribution name.

Changed

• Python version patch level bumps:

  • 3.8.15 -> 3.8.18

  • 3.9.17 -> 3.9.18

  • 3.10.12 -> 3.10.13

  • 3.11.4 -> 3.11.6

• (deps) Upgrade rules_go 0.39.1 -> 0.41.0; this is so gazelle integration works with upcoming Bazel versions

• (multi-version) Thedistribs attribute is no longer propagated. Thisattribute has been long deprecated by Bazel and shouldn’t be used.

• Calling//python:repositories.bzl#py_repositories() is required. It hasalways been documented as necessary, but it was possible to omit it in certaincases. An error about@rules_python_internal means thepy_repositories()call is missing inWORKSPACE.

• (bzlmod) Thepip.parse extension will generate os/arch specific lockfile entries onbazel>=6.4.

Added

• (bzlmod, entry_point) Addedpy_console_script_binary, whichallows adding custom dependencies to a package’s entry points and customizingthepy_binary rule used to build it.

• New Python versions available:3.8.17,3.11.5 usinghttps://github.com/indygreg/python-build-standalone/releases/tag/20230826.

• (gazelle) New#gazelle:python_generation_modefile directive to supportgenerating onepy_library per file.

• (python_repository) Supportnetrc andauth_patterns attributes to enableauthentication against private HTTP hosts serving Python toolchain binaries.

• //python:packaging_bzl added, abzl_library for the Starlarkfiles//python:packaging.bzl requires.

• (py_wheel) Added theincompatible_normalize_name feature flag tonormalize the package distribution name according to latest Pythonpackaging standards. Defaults toFalse for the time being.

• (py_wheel) Added theincompatible_normalize_version feature flagto normalize the package version according to PEP440 standard. Thisalso adds support for local version specifiers (versions with a+in them), in accordance with PEP440. Defaults toFalse for thetime being.

• New Python versions available:3.8.18,3.9.18,3.10.13,3.11.6,3.12.0 usinghttps://github.com/indygreg/python-build-standalone/releases/tag/20231002.3.12.0 support is considered beta and may have issues.

Removed

• (bzlmod) Theentry_point macro is no longer supported and has been removedin favour of thepy_console_script_binary macro forbzlmod users.

• (bzlmod) Thepip.parse no longer generates{hub_name}_{py_version} hub reposas theentry_point macro has been superseded bypy_console_script_binary.

• (bzlmod) Thepip.parse no longer generates{hub_name}_{distribution} hub repos.

Fixed

• (whl_library) No longer restarts repository rule when fetching externaldependencies improving initial build times involving external dependencyfetching.

• (gazelle) Improve runfiles lookup hermeticity.

Changed

• Python version patch level bumps:

  • 3.9.16 -> 3.9.17

  • 3.10.9 -> 3.10.12

  • 3.11.1 -> 3.11.4

• (bzlmod)pip.parse can no longer automatically use the defaultPython version; this was an unreliable and unsafe behavior. Thepython_version arg must always be explicitly specified.

Fixed

• (docs) Update docs to use correct bzlmod APIs and clarify how and when to usevarious APIs.

• (multi-version) Themain arg is now correctly computed and usually optional.

• (bzlmod)pip.parse no longer requires a call for whatever the configureddefault Python version is.

Added

• Created a changelog.

• (gazelle) Stop generating unnecessary imports.

• (toolchains) s390x supported for Python 3.9.17, 3.10.12, and 3.11.4.

Changed

• BREAKING (gazelle) Gazelle 0.30.0 or higher is required

• (bzlmod)@python_aliases renamed to `@python_versions

• (bzlmod)pip.parse argname renamed tohub_name

• (bzlmod)pip.parse argincompatible_generate_aliases removed and alwaystrue.

Fixed

• (bzlmod) Fixing Windows Python Interpreter symlink issues

• (py_wheel) Allow twine tags and args

• (toolchain, bzlmod) Restrict coverage tool visibility under bzlmod

• (pip) Ignore temporary pyc.NNN files in wheels

• (pip) Add format() calls to glob_exclude templates

• plugin_output in py_proto_library rule

Added

• Using Gazelle’s lifecycle manager to manage external processes

• (bzlmod)pip.parse can be called multiple times with different Pythonversions

• (bzlmod) Allow bzlmodpip.parse to reference the default python toolchain and interpreter

• (bzlmod) Implementing wheel annotations viawhl_mods

• (gazelle) support multiple requirements files in manifest generation

• (py_wheel) Support for specifyingDescription-Content-Type andSummary in METADATA

• (py_wheel) Support for specifyingProject-URL

• (compile_pip_requirements) Addedgenerate_hashes arg (default True) tocontrol generating hashes

• (pip) Create all_data_requirements alias

• Expose Python C headers through the toolchain.