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.

Title: when both maintainer and author provided, author discarded
Type: enhancement Stage:
Components: Distutils2, Documentation Versions: 3rd party
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: tarek Nosy List: akitada, eric.araujo, jbelmonte, skrah, tarek
Priority: normal Keywords:

Created on 2004-05-29 14:58 by jbelmonte, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (7)
msg60491 - (view) Author: John Belmonte (jbelmonte) * Date: 2004-05-29 14:58
When both maintainer and author contacts are passed to distutil's setup, the resulting PKG-INFO file has only an author field (set to the maintainer contact!).  The original author contact information is discarded.

Both maintainer and author contacts should be preserved.  If PKG-INFO doesn't support a maintainer contact, it should be added to the spec.
msg81140 - (view) Author: Akira Kitada (akitada) * Date: 2009-02-04 15:56
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
Platform: UNKNOWN
msg81142 - (view) Author: Tarek Ziadé (tarek) * (Python committer) Date: 2009-02-04 16:26
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 argument at all.

John, can you detail this ?
msg106752 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2010-05-30 09:24
Tarek, should we change component to Distutils2?
msg121004 - (view) Author: Éric Araujo (eric.araujo) * (Python committer) Date: 2010-11-12 01:23
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 file wants a contact point, so if the original author is not active anymore and there is another person acting as maintainer, the maintainer is the contact.

This is IMO a documentation bug, which I’m assigning to distutils2 (distutils docs only get quick fixes for things that don’t work at all).
msg121029 - (view) Author: Stefan Krah (skrah) * (Python committer) Date: 2010-11-12 09:26
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.
msg121030 - (view) Author: Tarek Ziadé (tarek) * (Python committer) Date: 2010-11-12 09:55
PEP 345 adds a Maintainer field to fix this, and this is now present and active in Ditsutils2. You can now have both.
Date User Action Args
2022-04-11 14:56:04adminsetgithub: 40308
2011-09-23 16:41:06eric.araujolinkissue13035 superseder
2011-09-02 16:13:47eric.araujolinkissue12840 superseder
2010-11-12 09:55:01tareksetstatus: open -> closed
resolution: fixed
messages: + msg121030
2010-11-12 09:26:37skrahsetnosy: + skrah
messages: + msg121029
2010-11-12 01:23:14eric.araujosetnosy: jbelmonte, tarek, eric.araujo, akitada
messages: + msg121004
components: + Documentation, Distutils2, - Distutils
versions: + 3rd party, - Python 3.1, Python 2.7
2010-05-30 09:24:40eric.araujosetnosy: + eric.araujo
messages: + msg106752
2009-02-04 16:26:37tareksetassignee: tarek
type: enhancement
messages: + msg81142
versions: + Python 3.1, Python 2.7
2009-02-04 15:56:53akitadasetnosy: + tarek, akitada
messages: + msg81140
2004-05-29 14:58:26jbelmontecreate