PEP 621: note that `license` could eventually have a "type" field
This commit is contained in:
parent
ba36cccc2d
commit
06d41486de
|
@ -242,9 +242,11 @@ error if the metadata specifies both keys.
|
||||||
|
|
||||||
A practical string value for the ``license`` key has been purposefully
|
A practical string value for the ``license`` key has been purposefully
|
||||||
left out to allow for a future PEP to specify support for SPDX_
|
left out to allow for a future PEP to specify support for SPDX_
|
||||||
expressions. If such support comes to fruition and a tool can
|
expressions (the same logic applies to any sort of "type" field
|
||||||
unambiguously identify the license specified, then the tool MAY
|
specifying what license the ``file`` or ``text`` represents). If such
|
||||||
fill in the appropriate trove classifier.
|
support comes to fruition and a tool can unambiguously identify the
|
||||||
|
license specified, then the tool MAY fill in the appropriate trove
|
||||||
|
classifiers.
|
||||||
|
|
||||||
``authors``/``maintainers``
|
``authors``/``maintainers``
|
||||||
'''''''''''''''''''''''''''
|
'''''''''''''''''''''''''''
|
||||||
|
|
Loading…
Reference in New Issue