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 lemburg
Recipients lemburg, pitrou, tarek, techtonik
Date 2009-09-29.14:56:43
SpamBayes Score 2.1085034e-10
Marked as misclassified No
Message-id <4AC22029.506@egenix.com>
In-reply-to <1254235530.27.0.87399883696.issue6992@psf.upfronthosting.co.za>
Content
Tarek Ziadé wrote:
> 
> Tarek Ziadé <ziade.tarek@gmail.com> added the comment:
> 
>> In order to clear up the inconsistency with maintainer 
>> not being a possible meta-data field, I think "Maintainer" 
>> should be added to the meta-data. Dito for "Maintainer-EMail".
> 
> Do you remember what's the story behind those two fields ?

I don't really remember, but suppose that the field was
added for cases where a package is being abandoned by the
original author and then maintained by someone new.

IMHO, the maintainer could have just added the new contact
details to the author field and a mention of the changed
maintenance to the description.

> I am not sure about the community usage of those since they are competng
> with author and author_email on setup() side

PyPI just shows the "Author" field, so if a package has different
author and maintainer entries, the author field is what's displayed -
not exactly useful, since bug reports and the like should normally
go to the maintainer, not the author.

Adding the maintainer field as well would resolve the issue.
History
Date User Action Args
2009-09-29 14:56:44lemburgsetrecipients: + lemburg, pitrou, techtonik, tarek
2009-09-29 14:56:43lemburglinkissue6992 messages
2009-09-29 14:56:43lemburgcreate