@@ -200,14 +200,14 @@ source, it is best to have Pip 10 on a manylinux1, macOS, or Windows system.
200
200
You can then build the SDists, or run any procedure that makes SDists
201
201
internally, like making wheels or installing. Since Pip itself
202
202
does not have an ` sdist ` command (it does have ` wheel ` and ` install ` ), you will
203
- need to use the ` pep517 ` package directly :
203
+ need to use the upcoming ` build ` package:
204
204
205
205
``` bash
206
206
# Normal package
207
- python3 -m pep517. build -s .
207
+ python3 -m build -s .
208
208
209
209
# Global extra
210
- PYBIND11_GLOBAL_SDIST=1 python3 -m pep517. build -s .
210
+ PYBIND11_GLOBAL_SDIST=1 python3 -m build -s .
211
211
```
212
212
213
213
If you want to use the classic "direct" usage of ` python setup.py ` , you will
@@ -232,7 +232,7 @@ When you invoke any `setup.py` command from the source directory, including
232
232
` pip wheel . ` and ` pip install . ` , you will activate a full source build. This
233
233
is made of the following steps:
234
234
235
- 1 . If the tool is PEP 518 compliant, like ` pep517. build` or Pip 10+, it will
235
+ 1 . If the tool is PEP 518 compliant, like ` build ` or Pip 10+, it will
236
236
create a temporary virtual environment and install the build requirements
237
237
(mostly CMake) into it. (if you are not on Windows, macOS, or a manylinux
238
238
compliant system, you can disable this with ` --no-build-isolation ` as long
0 commit comments