PEP 426 minor language cleanup
This commit is contained in:
parent
e46231b289
commit
8d1c599b2f
15
pep-0426.txt
15
pep-0426.txt
|
@ -38,9 +38,8 @@ format with no maximum line length, followed by a blank line and an
|
|||
arbitrary payload. It is parseable by the ``email`` module with an
|
||||
appropriate ``email.policy.Policy()``.
|
||||
|
||||
In Python 3.2, a serviceable read-only parser is::
|
||||
|
||||
email.parser.Parser().parsestr(metadata)
|
||||
When ``metadata`` is a Unicode string,
|
||||
```email.parser.Parser().parsestr(metadata)`` is a serviceable parser.
|
||||
|
||||
There are two standard locations for these metadata files:
|
||||
|
||||
|
@ -65,11 +64,11 @@ Fields
|
|||
This section specifies the names and semantics of each of the
|
||||
supported metadata fields.
|
||||
|
||||
Fields marked with "(optional)" may occur 0 or 1 times. Fields marked
|
||||
with "(multiple use)" may be specified 0, 1 or more times in a single
|
||||
metadata file. Only "Metadata-Version", "Name", "Version", and "Summary"
|
||||
must appear exactly once. The fields may appear in any order within
|
||||
the file.
|
||||
In a single Metadata 1.3 file, fields marked with "(optional)" may occur
|
||||
0 or 1 times. Fields marked with "(multiple use)" may be specified
|
||||
0, 1 or more times. Only "Metadata-Version", "Name", "Version", and
|
||||
"Summary" must appear exactly once. The fields may appear in any order
|
||||
within the file.
|
||||
|
||||
Metadata-Version
|
||||
::::::::::::::::
|
||||
|
|
Loading…
Reference in New Issue