New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when both maintainer and author provided, author discarded #40308
Comments
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. |
""" |
the Author metadata uses the maintainer field *or* the author field if 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 John, can you detail this ? |
Tarek, should we change component to Distutils2? |
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). |
I think this might be more than a documentation bug. Akira's example shows I'd prefer a separate maintainer field. |
PEP-345 adds a Maintainer field to fix this, and this is now present and active in Ditsutils2. You can now have both. |
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:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: