Éric Araujo added the comment:
This was already explained in #962772.
--
resolution: -> invalid
stage: -> committed/rejected
status: open -> closed
superseder: -> when both maintainer and author provided, author discarded
___
Python tracker
Éric Araujo added the comment:
> Is not simpler (to understand) to keep always the approach to keep both?
Well, there needs to be one point of contact. If someone takes the
responsibility to make a project available on PyPI without asking the author to
do it themselves, then that someone is r
Luca Fabbri added the comment:
I'm quite sure that after gettint ownership on an already existent package
(with a different author inside) and I added the maintainer (with my name) I
get the author override. But maybe I don't remember exactly...
Is not simpler (to understand) to keep always t
Éric Araujo added the comment:
I think this is intended behavior. When the author of a project is the one to
register with PyPI, they use the author and author_email fields, which get
displayed at PyPI. When it is not the original author but someone else who
packages and registers a project
New submission from Luca Fabbri :
I reported this problem in the pypi site issue tracker (issue 3396924):
https://sourceforge.net/tracker/?func=detail&atid=513503&aid=3396924&group_id=66150
However it seems that is a python bug.
If in one package's setup.py I provide maintainer (with email) and