[issue962772] when both maintainer and author provided, author discarded

Tarek Ziadé added the comment: PEP 345 adds a Maintainer field to fix this, and this is now present and active in Ditsutils2. You can now have both. -- resolution: -> fixed status: open -> closed ___ Python tracker

[issue962772] when both maintainer and author provided, author discarded

Stefan Krah added the comment: I think this might be more than a documentation bug. Akira's example shows that the maintainer is erroneously listed as the author. This does not seem fair to an author who in general will have written most of a package. I'd prefer a separate maintainer field. --

[issue962772] when both maintainer and author provided, author discarded

Éric Araujo added the comment: >From PEP 345: “Note that this field is intended for use when a project is >being maintained by someone other than the original author: it should be >omitted if it is identical to Author.” It’s therefore logical that maintainer wins over author: The metadata fil

[issue962772] when both maintainer and author provided, author discarded

Éric Araujo added the comment: Tarek, should we change component to Distutils2? -- nosy: +merwok ___ Python tracker ___ ___ Python-b

[issue962772] when both maintainer and author provided, author discarded

Tarek Ziadé added the comment: the Author metadata uses the maintainer field *or* the author field if the maintainer is not provided. What would be the rational to add a new maintainer field in the PKG-INFO ? In the first place, I am wondering what is the rational, today, to use the maintainer

[issue962772] when both maintainer and author provided, author discarded

Akira Kitada added the comment: """ from distutils.core import setup setup(name="foo", author="bar", maintainer="baz") """ gives me """ Metadata-Version: 1.0 Name: foo Version: 0.0.0 Summary: UNKNOWN Home-page: UNKNOWN Author: baz Author-email: UNKNOWN License: UNKNOWN Description: UNKNOWN Platf