On Mon, Nov 18, 2019 at 12:24 PM Paul G wrote:
> Was anyone on the list involved with the decision to use spaces in the spec?
> Is there some compelling reason we're missing to make the switch?
distutils was originally conceived and written by Greg Ward at CNRI,
back when Guido led a group there
I can envision a world where we migrate to space-separated everywhere, but I
think that would involve a decade of consumers supporting both until everyone
updates to a version of setuptools that emits spaces and I'm not sure it's
worth it.
Was anyone on the list involved with the decision to us
I don't have time to work on this and hope someone else can pick it up -
https://github.com/pypa/packaging-problems/issues/128 is a good issue to
use to keep track.
--
Distutils-SIG mailing list -- distutils-sig@python.org
To unsubscribe send an email to distutils-sig-le...@python.org
https://ma
Hi all,
The metadata specification shows the keyword field as a space separated list:
https://packaging.python.org/specifications/core-metadata/#keywords
PEP 566 backs that up, saying that the transformation to JSON should split that
field on whitespace:
https://www.python.org/dev/peps/pep-0566/
