>From "[distutils] Multiple package authors" [1]
- How should multiple author-email and maintainer-email addresses be
specified?
- Should we add security-email and/or security-disclosure-instructions?
[1] http://markmail.org/thread/xmwfktnsbmpakv6b
On Wednesday, December 6, 2017, Nick Coghlan
There are author-email and maintainer-email fields.
You could also or instead use a mailing list address for the author-email
or maintainer-email fields. Newlines work (just like file\nnames)?
With a mailing list, package maintainers can share responsibility (*) and
hand off correspondence
I think I implicitly knew this, but as I've just released a package (to
be announced soon) that actually has multiple authors, I found out first
hand that PyPI rejects uploads where the author-email field isn't a
completely valid email address, and that there is no support for
multiple author
> I don’t know how much we can or should define “being used”. For instance,
every package in existence is going to be downloaded via mirroring, so we
can’t go by pure download counts (and some mirrors just use pip to do their
downloading) and we’re going to need to interpret the download counts to
As Donald and Nick mentioned last month,[0] several folks are -- thanks
to Mozilla Open Source Support -- working on deploying Warehouse and
making PyPI more sustainable. I'm the main project manager on this
effort and am putting notes on wiki.python.org as we go.[1]
Ernest W. Durbin III gave the
> On Nov 29, 2017, at 11:10 PM, Sumana Harihareswara wrote:
>
> While getting up to speed on Warehouse I saw how many package transfer
> requests are waiting for PEP 541[0] to be accepted, so I thought it
> might be helpful to round up what I see as the outstanding