[Catalog-sig] [Proposal] Registered packages must provide the source code distribution on PyPI

Mark Ramm mark at geek.net
Thu Jun 17 16:15:06 CEST 2010

This would also impact projects like turbogears (perhaps we're the
only one, I don't know) that point to our own pypi compatable index
with the download URL.   We do this because then we can fix things
like packages with no windows eggs, packages that are broken on PyPi
or whatever.   And to help control which versions of which packages
get installed by settuptools/distribute when you easy_install tg.

I'm fine with putting sdists up on pypi, but still want people to be
downloading files from our controlled index by default where possible.

--Mark Ramm

On Thu, Jun 17, 2010 at 2:58 AM, "Martin v. Löwis" <martin at v.loewis.de> wrote:
>> I propose a policy change for packages registered with PyPI:
>>  - packages registered on PyPI have at least one release
>>  - one release of registered package on PyPI _must_ contain
>>    a valid source code distribution (sdist)
>>  - packages registered on PyPI without releases or without
>>    source code release are subject to be removed after N days
>>    after the day of registration
> So how would you implement that policy change? Please propose a phased
> approach, that gives affected people plenty of options to intervene if
> they disagree with the policy.
> Regards,
> Martin
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org
> http://mail.python.org/mailman/listinfo/catalog-sig

More information about the Catalog-SIG mailing list