Repository navigation
PKG-INFO file should differentiate between authors and maintainers #47936
Description
| BPO | 3686 |
|---|---|
| Nosy | @malemburg, @tarekziade, @merwok, @akitada |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = 'https://github.com/tarekziade'
closed_at = <Date 2010-05-16.12:39:35.700>
created_at = <Date 2008-08-26.08:32:32.689>
labels = ['type-feature']
title = 'PKG-INFO file should differentiate between authors and maintainers'
updated_at = <Date 2010-05-16.12:39:35.698>
user = 'https://github.com/malemburg'bugs.python.org fields:
activity = <Date 2010-05-16.12:39:35.698>
actor = 'tarek'
assignee = 'tarek'
closed = True
closed_date = <Date 2010-05-16.12:39:35.700>
closer = 'tarek'
components = ['Distutils2']
creation = <Date 2008-08-26.08:32:32.689>
creator = 'lemburg'
dependencies = []
files = []
hgrepos = []
issue_num = 3686
keywords = []
message_count = 4.0
messages = ['71970', '81368', '81369', '105865']
nosy_count = 4.0
nosy_names = ['lemburg', 'tarek', 'eric.araujo', 'akitada']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue3686'
versions = ['Python 3.1', 'Python 2.7']
Activity
malemburg commentedon Aug 26, 2008
The PKG-INFO file currently only provides an "Authors" field which is
mapped to the DistributionMetadata.get_contact() information.
However, the latter method is really meant to provide access to contact
information and not authorship, which is why it prefers the maintainer
infos over the actual author infos.
As a result, the maintainer can appear as author in the PKG-INFO file,
which is wrong.
Ideal would be to have both an "Author" and "Maintainer" field in the
PKG-FILE with 1-1 mappings to the setup() parameters.
akitada commentedon Feb 8, 2009
Maintainer field is not specified in PEP-241, PEP-314 and even PEP-345.
Can we add this field to PEP-345?
tarekziade commentedon Feb 8, 2009
The point is, the current implementation of Distutils will take the
maintainer *or* the author for the Author field.
So this relates to bpo-962772 : do we want to keep maintainer and
maintainer_email at all ?
I'll push a mail in Distutils-SIG about this.
tarekziade commentedon May 16, 2010
This is now defined in PEP-345 and implemented in Distutils2.