Skip to content

Commit 589b945

Browse files
authored
PEP 621: clarify what the text field for license represents
1 parent 5cedff4 commit 589b945

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

pep-0621.rst

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -248,8 +248,9 @@ The table may have one of two keys. The ``file`` key has a string
248248
value that is a relative file path to the file which contains the
249249
license for the project. Tools MUST assume the file's encoding is
250250
UTF-8. The ``text`` key has a string value which is the license of the
251-
project. These keys are mutually exclusive, so a tool MUST raise an
252-
error if the metadata specifies both keys.
251+
project whose meaning is that of the ``License`` field from the
252+
`core metadata`_. These keys are mutually exclusive, so a tool MUST
253+
raise an error if the metadata specifies both keys.
253254

254255
A practical string value for the ``license`` key has been purposefully
255256
left out to allow for a future PEP to specify support for SPDX_

0 commit comments

Comments
 (0)