This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients lemburg, pitrou, tarek, techtonik
Date 2009-09-29.13:31:58
SpamBayes Score 4.1469637e-05
Marked as misclassified No
Message-id <1254231334.5445.21.camel@localhost>
In-reply-to <1254230892.05.0.722067747602.issue6992@psf.upfronthosting.co.za>
Content
> Replacing the author/author_email/maintainer/maintainer_email mess with
> a single authors argument, that fills a multi-valued "Author" metadata
> field make it clearer.

What does changing the type of the "author" field make clearer exactly?
It is a field for human beings to read, and a human being is perfectly
able to parse "AP <ap@example.com>, Tarek <tarek@example.com>" without
the help of a computer.

While there may be some things to clear up in the current metadata, this
shouldn't be a pretext to gratuitously change things that are ok. I'm
bothered that many people currently seem to think that it's ok to break
compatibility for whatever non-critical reason. This is not the way we
will make Python a reliable platform to use and develop for.
History
Date User Action Args
2009-09-29 13:32:00pitrousetrecipients: + pitrou, lemburg, techtonik, tarek
2009-09-29 13:31:58pitroulinkissue6992 messages
2009-09-29 13:31:58pitroucreate