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:54:34
SpamBayes Score 6.286154e-08
Marked as misclassified No
Message-id <1254232690.5445.30.camel@localhost>
In-reply-to <1254231902.01.0.0642377880596.issue6992@psf.upfronthosting.co.za>
Content
> I am bothered that more and more are people constantly jumping on my
> back everytime I try to make Distutils evolves a bit or everytime I
> discuss some feature proposals with the community.

This is not "jumping on your back", this is being skeptical about a
detail that doesn't seem to warrant a change. It is still unknown what
use case the new "author" scheme would solve that the old one doesn't
(does someone want the "author" field to be machine parsable? for what
purpose?), and this bug report itself is quite nebulous (it is unsure
what "doesn't work" since you can put human-readable info about multiple
authors in a single unicode string).
That's why I call it "gratuitous".

> But saying that making the metadata evolve "is not the way we will make
> Python a reliable platform to use and develop for" is completely
> wrong imho.

A metadata system, by definition, has to remain reasonably stable (or be
version-numbered, such that old metadata can be recognized properly).
You can certainly add fields, but replacing existing fields with others
should be sufficiently motivated.

If the ID3 spec was rewritten every five years so that you couldn't read
back the author info from the MP3s you made in 2000, you wouldn't be
very happy :)
History
Date User Action Args
2009-09-29 13:54:35pitrousetrecipients: + pitrou, lemburg, techtonik, tarek
2009-09-29 13:54:34pitroulinkissue6992 messages
2009-09-29 13:54:34pitroucreate