@@ -16,7 +16,7 @@ And of course *setuptools* itself is not deprecated either.
16
16
17
17
It is however deprecated to run ``python setup.py `` as a command line tool.
18
18
19
- This means for example that the following commands **MUST NOT ** be run anymore:
19
+ This means that commands such as the following **MUST NOT ** be run anymore:
20
20
21
21
* ``python setup.py install ``
22
22
* ``python setup.py develop ``
@@ -28,7 +28,7 @@ What commands should be used instead?
28
28
=====================================
29
29
30
30
+---------------------------------+----------------------------------------+
31
- | Deprecated | Current recommendation |
31
+ | Deprecated | Recommendation |
32
32
+=================================+========================================+
33
33
| ``python setup.py install `` | ``python -m pip install . `` |
34
34
+---------------------------------+----------------------------------------+
@@ -79,6 +79,33 @@ The command ``python setup.py install`` was deprecated
79
79
in setuptools version *58.3.0 *.
80
80
81
81
82
+ What about other commands?
83
+ ==========================
84
+
85
+ .. rubric :: ``python setup.py test``
86
+
87
+ The recommendation is to use a test runner such as pytest _.
88
+
89
+ .. _pytest : https://docs.pytest.org/
90
+
91
+
92
+ .. rubric :: ``python setup.py check`` and ``python setup.py upload``
93
+
94
+ A trusted replacement is :ref: `twine `:
95
+
96
+ * ``python -m twine check ``
97
+ * ``python -m twine upload ``
98
+
99
+
100
+ .. rubric :: ``python setup.py --version``
101
+
102
+ A possible replacement solution (among others) is to rely on setuptools-scm _:
103
+
104
+ * ``python -m setuptools-scm ``
105
+
106
+ .. _setuptools-scm : https://setuptools-scm.readthedocs.io/en/latest/usage/#as-cli-tool
107
+
108
+
82
109
What about custom commands?
83
110
===========================
84
111
0 commit comments