fix: define rules_python_internal earlier so Bazel 9 doesn't try to use PyInfo et al builtins (#2485) For Bazel 9 workspace builds, if `@rules_python_internal` isn't defined early enough, an earlier version of `@rules_python` gets defined and the logic to not use the builtin PyInfo et al symbols doesn't occur. Since Bazel 9 doesn't have these builtins, an error occurs. This seems to only happen if the main module is rules_python. The example workspaces don't see to have an issue. I'm not sure why, but it seems similar to the behavior where autoloading is disabled for specific repos, rules_python among them. To fix, move the `@rules_python_internal` repo definition to be earlier in the WORKSPACE processing. With that repo defined, the conditional logic takes place, and things seem to be happy.
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.