Hi,
I've just one suggestion after reading PEP 426. It is about the
Project-URL description and the implicit ordering of its fields.
Project-URL (multiple use)
::::::::::::::::::::::::::
A string containing a browsable URL for the project and a label for it,
separated by a comma.
Example::
Bug Tracker, http://bitbucket.org/tarek/distribute/issues/
The label is a free text limited to 32 signs.
Perhaps the description could be reworded so the field ordering in the
example (label, URL) and the description (URL, label) aren't contradictory.
I would find the following text less confusing:
Project-URL (multiple use)
::::::::::::::::::::::::::
A string containing a label for the project and a browsable URL for it,
separated by a comma.
Example::
Bug Tracker, http://bitbucket.org/tarek/distribute/issues/
The label is a free text limited to 32 signs.
Or is it that there's no mandatory order and the implementations should
detect which one is the URL?
Regards, and thanks for the great work you are doing,
Rafael Villar Burke
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
