This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients dstufft, eric.araujo, jugmac00
Date 2019-11-26.14:20:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1574778016.32.0.670234618814.issue38914@roundup.psfhosted.org>
In-reply-to
Content
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)
History
Date User Action Args
2019-11-26 14:20:16eric.araujosetrecipients: + eric.araujo, dstufft, jugmac00
2019-11-26 14:20:16eric.araujosetmessageid: <1574778016.32.0.670234618814.issue38914@roundup.psfhosted.org>
2019-11-26 14:20:16eric.araujolinkissue38914 messages
2019-11-26 14:20:16eric.araujocreate