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