I agree but have simply not had time. Edit it to add something like "Instead of a description header, the description may be provided in the message body, e.g. after a completely blank line to end the headers, followed by the long description with no indentation or other special formatting needed". Write something about putting the body back into a description key in the json version. Just delete the example parsing code which doesn't parse message bodies. I don't recall any other issues that would prevent approval.
On Thu, Feb 15, 2018 at 11:14 AM Thomas Kluyver <tho...@kluyver.me.uk> wrote: > I'd like to once again prod this PEP towards completion: > > https://www.python.org/dev/peps/pep-0566/ > > The version numbering question has been decided in favour of calling it > 2.1. > > The remaining question I'm aware of is whether to make the body text (in > the email format of the metadata file) officially represent the package > long description. I'm in favour of doing so: at least twine and flit > already use this for metadata in wheels. > > Thomas > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig >
_______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig