pep-0426: remove extras from Setup-Requires-Dist
Today Setup-Requires-Dist is needed so that "python setup.py" will run at all. Pip executes setup.py to write the requirements to a file, installs them, and runs setup.py again to do the build/install. Not prepared to add extras to this stage as installing a package with extras would have different results depending on whether you were installing package[extra] from source or from a binary.
This commit is contained in:
parent
0a825fe2ee
commit
2cda64a532
18
pep-0426.txt
18
pep-0426.txt
|
@ -392,9 +392,6 @@ package or install the distribution. Commonly used to bring in extra
|
||||||
compiler support or a package needed to generate a manifest from
|
compiler support or a package needed to generate a manifest from
|
||||||
version control.
|
version control.
|
||||||
|
|
||||||
Distributions may also depend on optional features of other distributions.
|
|
||||||
See `Optional Features`_ for details.
|
|
||||||
|
|
||||||
Examples::
|
Examples::
|
||||||
|
|
||||||
Setup-Requires-Dist: custom_setup_command
|
Setup-Requires-Dist: custom_setup_command
|
||||||
|
@ -1086,8 +1083,7 @@ Optional features
|
||||||
|
|
||||||
Distributions may use the ``Provides-Extra`` field to declare additional
|
Distributions may use the ``Provides-Extra`` field to declare additional
|
||||||
features that they provide. Environment markers may then be used to indicate
|
features that they provide. Environment markers may then be used to indicate
|
||||||
that particular dependencies (as specified in ``Requires-Dist`` or
|
that particular dependencies are needed only when a particular optional
|
||||||
``Setup-Requires-Dist``) are needed only when a particular optional
|
|
||||||
feature has been requested.
|
feature has been requested.
|
||||||
|
|
||||||
Other distributions then require an optional feature by placing it
|
Other distributions then require an optional feature by placing it
|
||||||
|
@ -1095,10 +1091,9 @@ inside square brackets after the distribution name when declaring the
|
||||||
dependency. Multiple features can be requisted by separating them with a
|
dependency. Multiple features can be requisted by separating them with a
|
||||||
comma within the brackets.
|
comma within the brackets.
|
||||||
|
|
||||||
The full set of dependency requirements is then the union of the
|
The full set of dependency requirements is then the union of the sets
|
||||||
sets created by first evaluating the `Requires-Dist` (or
|
created by first evaluating the `Requires-Dist` fields with `extra`
|
||||||
`Setup-Requires-Dist`) fields with `extra` set to `None` and then to
|
set to `None` and then to the name of each requested feature.
|
||||||
the name of each requested feature.
|
|
||||||
|
|
||||||
Example::
|
Example::
|
||||||
|
|
||||||
|
@ -1159,9 +1154,8 @@ Summary of differences from \PEP 345
|
||||||
* Optional feature mechanism
|
* Optional feature mechanism
|
||||||
|
|
||||||
* the new ``Provides-Extra`` field
|
* the new ``Provides-Extra`` field
|
||||||
* ``extra`` expression defined for environment markers.
|
* ``extra`` expression defined for environment markers
|
||||||
* optional feature support in ``Requires-Dist`` and
|
* optional feature support in ``Requires-Dist``
|
||||||
``Setup-Requires-Dist``
|
|
||||||
|
|
||||||
* Metadata extension mechanism
|
* Metadata extension mechanism
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue