You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,12 +39,12 @@ the older way of configuring bazel with a `WORKSPACE` file.
39
39
### Using bzlmod
40
40
41
41
To import rules_python in your project, you first need to add it to your
42
-
`MODULES.bazel` file, using the snippet provided in the
42
+
`MODULE.bazel` file, using the snippet provided in the
43
43
[release you choose](https://github.com/bazelbuild/rules_python/releases).
44
44
45
45
#### Toolchain registration with bzlmod
46
46
47
-
To register a hermetic Python toolchain rather than rely on a system-installed interpreter for runtime execution, you can add to the `MODULES.bazel` file:
47
+
To register a hermetic Python toolchain rather than rely on a system-installed interpreter for runtime execution, you can add to the `MODULE.bazel` file:
48
48
49
49
```python
50
50
# Find the latest version number here: https://github.com/bazelbuild/rules_python/releases
@@ -161,7 +161,7 @@ target in the appropriate wheel repo.
161
161
162
162
#### Using bzlmod
163
163
164
-
To add pip dependencies to your `MODULES.bazel` file, use the `pip.parse` extension, and call it to create the
164
+
To add pip dependencies to your `MODULE.bazel` file, use the `pip.parse` extension, and call it to create the
165
165
central external repo and individual wheel external repos.
0 commit comments