-
Notifications
You must be signed in to change notification settings - Fork 968
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
Email attributed to wrong project author #14813
Comments
The order of the |
Regardless of ordering, surely it is a bug to display one author's name with a different author's email address on the package index? And especially if the author list is considered unordered, displaying the email address of the first author in This behavior is described exactly by a comment on #9400, in fact: One author without an email address associated is displayed as the name on PyPI, with the email address of another entry. |
Since pypi/warehouse#9400 and pypi/warehouse#14813 (perhaps others too) remain unresolved, let's keep our metadata simple. Incomplete metadata— i.e. the email addresses this commit removes—is the only thing worse than straight-up *incorrect* metadata. We don't want any author or maintainer names to be attached to the wrong email addresses on the published package page.
Marking as blocked for same issue as noted in #16496 (comment) |
Describe the bug
If a project defines multiple authors, and the first author does not list an email, PyPI will erroneously attribute the first email address in the metadata to that first author.
Expected behavior
PyPI should not attribute any email to the first author if one is not given.
To Reproduce
See an example here: https://pypi.org/project/sopel-iplookup/1.0.0/
The project's authorship metadata looks like:
Where there is no email listed for Dimitri Molenaars. On the PyPI project page linked above, however, the address
[email protected]
is attributed to this author.The generated
METADATA
splits this information across theAuthor
andAuthor-email
fields, which may be related to the bug.My Platform
N/A
Additional context
The closest open issue I can find is #9400, but that seems distinct.
The text was updated successfully, but these errors were encountered: