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.
Created on 2011年08月25日 07:22 by keul, last changed 2022年04月11日 14:57 by admin. This issue is now closed.
| Messages (5) | |||
|---|---|---|---|
| msg142959 - (view) | Author: Luca Fabbri (keul) | Date: 2011年08月25日 07:22 | |
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 author (whit email) after the "python setup.py register ... upload" I create a new package where I see the maintainer as a creator. If I manually fix it through the pypi user interface all works, so seems that this is only a bug of the register procedure. |
|||
| msg142971 - (view) | Author: Éric Araujo (eric.araujo) * (Python committer) | Date: 2011年08月25日 15:47 | |
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, then they fill author and maintainer entries, and PyPI uses the maintainer/maintainer_email values as person to contact. |
|||
| msg142974 - (view) | Author: Luca Fabbri (keul) | Date: 2011年08月25日 16:08 | |
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 the approach to keep both? |
|||
| msg142978 - (view) | Author: Éric Araujo (eric.araujo) * (Python committer) | Date: 2011年08月25日 16:22 | |
> 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 responsible for the PyPI distribution. |
|||
| msg143410 - (view) | Author: Éric Araujo (eric.araujo) * (Python committer) | Date: 2011年09月02日 16:13 | |
This was already explained in #962772. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:57:21 | admin | set | github: 57049 |
| 2011年09月02日 16:13:47 | eric.araujo | set | status: open -> closed resolution: not a bug messages: + msg143410 superseder: when both maintainer and author provided, author discarded stage: resolved |
| 2011年08月25日 16:22:08 | eric.araujo | set | messages: + msg142978 |
| 2011年08月25日 16:08:25 | keul | set | messages: + msg142974 |
| 2011年08月25日 15:47:38 | eric.araujo | set | messages: + msg142971 |
| 2011年08月25日 07:22:35 | keul | create | |