8000 type:docs Update README.md (#1186) · chrislovecnm/rules_python@c20aa1a · GitHub
[go: up one dir, main page]

Skip to content

Commit c20aa1a

Browse files
authored
type:docs Update README.md (bazel-contrib#1186)
Change instruction to refer to `MODULE.bazel` instead of `MODULES.bazel`.
1 parent 1d1efe9 commit c20aa1a
Copy full SHA for c20aa1a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -39,12 +39,12 @@ the older way of configuring bazel with a `WORKSPACE` file.
3939
### Using bzlmod
4040

4141
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
4343
[release you choose](https://github.com/bazelbuild/rules_python/releases).
4444

4545
#### Toolchain registration with bzlmod
4646

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:
4848

4949
```python
5050
# Find the latest version number here: https://github.com/bazelbuild/rules_python/releases
@@ -161,7 +161,7 @@ target in the appropriate wheel repo.
161161

162162
#### Using bzlmod
163163

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
165165
central external repo and individual wheel external repos.
166166

167167
```python

0 commit comments

Comments
 (0)
0