- include an example of Python-Requires + environment markers
- allow a bare Extension field (and give an example use case)
- be explicit that projects that refuse to use compliant version
numbering must continue to use metadata v1.1
- add guidelines for sorting across metadata versions
- add guidelines for dependencies across metadata versions
- point out that the new sort order is more consistent with that
of pkg_resources
- mention the implicit test and doc features in the rationale
for supporting optional features in general
- consistently use sentence case for headings, instead of a mix
of sentence case and title case
- other typo fixes
- better explain the new description format
- rationale for why Obsoletes-Dist header was removed
- rationale for why Description header was retained
- miscellaneous formatting and editorial fixes
This tries to create a slightly easier to read ordering for the
field descriptions. Roughly:
- basic metadata
- URLs
- contacts
- licensing & classifiers
- what the distribution provides
- what the distribution needs
- extended metadata
Nick Coghlan
Daniel Holth