Commit b11f077
authored
fix: define rules_python_internal earlier so Bazel 9 doesn't try to use PyInfo et al builtins (bazel-contrib#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.1 parent 7fd5191 commit b11f077
2 files changed
Lines changed: 2 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
16 | 16 | | |
17 | 17 | | |
18 | 18 | | |
| 19 | + | |
19 | 20 | | |
20 | 21 | | |
21 | 22 | | |
| |||
39 | 40 | | |
40 | 41 | | |
41 | 42 | | |
| 43 | + | |
42 | 44 | | |
43 | 45 | | |
44 | 46 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
25 | 25 | | |
26 | 26 | | |
27 | 27 | | |
28 | | - | |
29 | 28 | | |
30 | 29 | | |
31 | 30 | | |
32 | 31 | | |
33 | 32 | | |
34 | 33 | | |
35 | | - | |
36 | 34 | | |
37 | 35 | | |
38 | 36 | | |
| |||
0 commit comments