Metadata 1.3 tweaks
This commit is contained in:
parent
e444fb4ec8
commit
5d5e04fe53
29
pep-0426.txt
29
pep-0426.txt
|
@ -155,11 +155,11 @@ markup is optional; programs can also display the contents of the
|
|||
field as-is. This means that authors should be conservative in
|
||||
the markup they use.
|
||||
|
||||
To support empty lines and lines with indentation with respect to
|
||||
the RFC 822 format, any CRLF character has to be suffixed by 7 spaces
|
||||
followed by a pipe ("|") char. As a result, the Description field is
|
||||
encoded into a folded field that can be interpreted by RFC822
|
||||
parser [2]_.
|
||||
To support empty lines and lines with indentation and maintain
|
||||
compatibility with ``email.parser.Parser()``, any CRLF character has to
|
||||
be suffixed by 7 spaces followed by a pipe ("|") char. As a result, the
|
||||
Description field is encoded into a folded field that can be interpreted
|
||||
by RFC822 parser [2]_.
|
||||
|
||||
Example::
|
||||
|
||||
|
@ -221,9 +221,9 @@ Example::
|
|||
Author-email (optional)
|
||||
:::::::::::::::::::::::
|
||||
|
||||
A string containing the author's e-mail address. It can contain
|
||||
a name and e-mail address in the legal forms for a RFC-822
|
||||
``From:`` header.
|
||||
A string containing the author's e-mail address. It contains a name
|
||||
and e-mail address in the RFC 5322 recommended ``Address Specification``
|
||||
format.
|
||||
|
||||
Example::
|
||||
|
||||
|
@ -249,9 +249,8 @@ Example::
|
|||
Maintainer-email (optional)
|
||||
:::::::::::::::::::::::::::
|
||||
|
||||
A string containing the maintainer's e-mail address. It can contain
|
||||
a name and e-mail address in the legal forms for a RFC-822
|
||||
``From:`` header.
|
||||
A string containing the maintainer's e-mail address. It has the same
|
||||
format as ``Author-email``.
|
||||
|
||||
Note that this field is intended for use when a project is being
|
||||
maintained by someone other than the original author: it should be
|
||||
|
@ -268,7 +267,7 @@ License (optional)
|
|||
Text indicating the license covering the distribution where the license
|
||||
is not a selection from the "License" Trove classifiers. See
|
||||
"Classifier" below. This field may also be used to specify a
|
||||
particular version of a licencse which is named via the ``Classifier``
|
||||
particular version of a license which is named via the ``Classifier``
|
||||
field, or to indicate a variation or exception to such a license.
|
||||
|
||||
Examples::
|
||||
|
@ -426,7 +425,7 @@ Examples::
|
|||
Requires-External: libpng (>=1.5)
|
||||
|
||||
|
||||
Project-URL (multiple-use)
|
||||
Project-URL (multiple use)
|
||||
::::::::::::::::::::::::::
|
||||
|
||||
A string containing a browsable URL for the project and a label for it,
|
||||
|
@ -480,12 +479,12 @@ It is legal to specify `Provides-Extra` without referencing it in any
|
|||
not been declared with `Provides-Extra`.
|
||||
|
||||
|
||||
Extension (multiple-use)
|
||||
Extension (multiple use)
|
||||
::::::::::::::::::::::::
|
||||
|
||||
An ASCII string, not containing whitespace or the / character, that
|
||||
indicates the presence of extended metadata. Additional tags defined by
|
||||
an `Extension: Chili` should be of the form `Chili/Name`::
|
||||
an `Extension: Chili` must be of the form `Chili/Name`::
|
||||
|
||||
Extension: Chili
|
||||
Chili/Type: Poblano
|
||||
|
|
Loading…
Reference in New Issue