|  | 
| 1 | 1 | (build-interface)= | 
| 2 | 2 | 
 | 
| 3 |  | -```{versionadded} 10.0 | 
| 4 |  | -
 | 
| 5 |  | -``` | 
| 6 |  | - | 
| 7 |  | -```{versionchanged} 23.1 | 
| 8 |  | -The legacy interface where pip could invoke `setup.py install` | 
| 9 |  | -in some circumstances was removed, | 
| 10 |  | -in favor of the fallback behavior described below. | 
| 11 |  | -``` | 
| 12 |  | - | 
| 13 |  | -```{versionchanged} 25.3 | 
| 14 |  | -The legacy interface where pip could invoke `setup.py build_wheel` or | 
| 15 |  | -`setup.py develop` in some circumstances was removed, | 
| 16 |  | -in favor of the fallback behavior described below.. | 
| 17 |  | -``` | 
| 18 |  | - | 
| 19 | 3 | # Build System Interface | 
| 20 | 4 | 
 | 
| 21 | 5 | When dealing with installable source distributions of a package, pip does not | 
| @@ -173,14 +157,36 @@ passed. | 
| 173 | 157 | 
 | 
| 174 | 158 | ## Historical notes | 
| 175 | 159 | 
 | 
|  | 160 | +```{versionadded} 10.0 | 
|  | 161 | +
 | 
|  | 162 | +``` | 
|  | 163 | + | 
| 176 | 164 | As this feature was incrementally rolled out, there have been various notable | 
| 177 | 165 | changes and improvements in it. | 
| 178 | 166 | 
 | 
| 179 |  | -- setuptools 40.8.0 is the first version of setuptools that offers a | 
| 180 |  | -  {pep}`517` backend that closely mimics directly executing `setup.py`. | 
| 181 |  | -- Prior to pip 18.0, pip only supports installing build requirements from | 
| 182 |  | -  wheels, and does not support the use of environment markers and extras (only | 
| 183 |  | -  version specifiers are respected). | 
| 184 |  | -- Prior to pip 18.1, build dependencies using `.pth` files are not properly | 
| 185 |  | -  supported; as a result namespace packages do not work under Python 3.2 and | 
| 186 |  | -  earlier. | 
|  | 167 | +Setuptools 40.8.0 is the first version of setuptools that offers a | 
|  | 168 | +{pep}`517` backend that closely mimics directly executing `setup.py`. | 
|  | 169 | + | 
|  | 170 | +```{versionadded} 18.0 | 
|  | 171 | +Prior to pip 18.0, pip only supports installing build requirements from | 
|  | 172 | +wheels, and does not support the use of environment markers and extras (only | 
|  | 173 | +version specifiers are respected). | 
|  | 174 | +``` | 
|  | 175 | + | 
|  | 176 | +```{versionadded} 18.1 | 
|  | 177 | +Prior to pip 18.1, build dependencies using `.pth` files are not properly | 
|  | 178 | +supported; as a result namespace packages do not work under Python 3.2 and | 
|  | 179 | +earlier. | 
|  | 180 | +``` | 
|  | 181 | + | 
|  | 182 | +```{versionchanged} 23.1 | 
|  | 183 | +The legacy interface where pip could invoke `setup.py install` | 
|  | 184 | +in some circumstances was removed, | 
|  | 185 | +in favor of the fallback behavior described above. | 
|  | 186 | +``` | 
|  | 187 | + | 
|  | 188 | +```{versionchanged} 25.3 | 
|  | 189 | +The legacy interface where pip could invoke `setup.py build_wheel` or | 
|  | 190 | +`setup.py develop` in some circumstances was removed, | 
|  | 191 | +in favor of the fallback behavior described above. | 
|  | 192 | +``` | 
0 commit comments