Correct backward compatible update logic (#1588)
This commit is contained in:
parent
69de6be4a9
commit
b71941a239
11
pep-0631.rst
11
pep-0631.rst
|
@ -57,10 +57,13 @@ Every element SHOULD be an `entry <#entries>`_.
|
||||||
'subprocess32; python_version < "3.2"',
|
'subprocess32; python_version < "3.2"',
|
||||||
]
|
]
|
||||||
|
|
||||||
Any element MAY be an inline table to support possible future functionality.
|
Future versions of this specification that allow for any element to be an inline
|
||||||
Backends MUST error when encountering these until the specification is extended.
|
table should be considered backwards compatible, and consumers of the ``[project]``
|
||||||
Other parsers SHOULD do the same, though they MAY consider the entire enclosing
|
table should take this into consideration.
|
||||||
field as `dynamic`_.
|
|
||||||
|
Backends MUST error when encountering these unless the specification is extended;
|
||||||
|
other parsers, particularly those not intended to be listed in a project's
|
||||||
|
``build-system.requires``, SHOULD consider the entire enclosing field as `dynamic`_.
|
||||||
|
|
||||||
optional-dependencies
|
optional-dependencies
|
||||||
---------------------
|
---------------------
|
||||||
|
|
Loading…
Reference in New Issue