You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
assignee=Noneclosed_at=<Date2020-10-07.23:46:10.569>created_at=<Date2019-11-26.09:41:10.985>labels= ['3.8', 'type-bug', 'library', '3.9']
title='Clarify wording for warning message when checking a package'updated_at=<Date2020-11-13.15:20:35.741>user='https://github.com/jugmac00'
I ported a 16 year old package to Python 3, and tried to upload it to PyPi. I know the author name, but not his email address. Also, I think he does not like to get bothered with emails for a project he abandoned 16 years ago.
P.S.: I am working on a PR for this and update this issue accordingly.
For your project, if you define maintainer and maintainer-email (with your own info), it’s too bad that adding author results in a warning for missing author-email!
The goal of these checks as I understand them is a best effort to encourage projects to contain contact information (and recognition for the work). It seems legitimate to know the original author name but not email, and too bad that the simplest way to avoid the warning is to remove the author info.
I wonder if it would be going too far to change the checks to avoid the warning if we have author, maintainer and maintainer-email (or even more combinations? given that email format allows embedding a name directly there)
For the future, we generally tend to keep distutils pretty "frozen", only making minor changes or the changes needed to build Python itself. Instead we generally make changes in setuptools, which for the moment monkey-patches distutils (and into which distutils will eventually be merged). One of the big reasons is that setuptools is used across all versions of Python, so the changes are automatically backported, whereas changes to distutils will only be seen by people using the most recent Python versions.
In this case, it's not really a substantive change, so I think we can leave it in distutils, I just wanted to bring this up as an FYI.