Skip to content

PKG-INFO file should differentiate between authors and maintainers #47936

Description

@malemburg
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

  1. malemburg commented on Aug 26, 2008

    @malemburg
    MemberAuthor

    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.

  2. added
    stdlibStandard Library Python modules in the Lib/ directory
    on Aug 26, 2008
  3. akitada commented on Feb 8, 2009

    akitadamannequin
    Mannequin

    Maintainer field is not specified in PEP-241, PEP-314 and even PEP-345.
    Can we add this field to PEP-345?

  4. tarekziade commented on Feb 8, 2009

    tarekziademannequin
    Mannequin

    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.

  5. self-assigned this
    on Feb 8, 2009
  6. tarekziade commented on May 16, 2010

    tarekziademannequin
    Mannequin

    This is now defined in PEP-345 and implemented in Distutils2.

  7. removed
    stdlibStandard Library Python modules in the Lib/ directory
    on May 16, 2010
  8. transferred this issue fromon Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

type-featureA feature request or enhancement

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions