[Catalog-sig] pre-PEP: transition to release-file hosting at pypi site
regebro at gmail.com
Mon Mar 11 09:18:28 CET 2013
On Mon, Mar 11, 2013 at 9:06 AM, Ronald Oussoren <ronaldoussoren at mac.com> wrote:
> But this isn't necessarily true, there is another solution: mirror your requirements locally.
I do that. This is not a solution, because your requirements yesterday
is not your requirements tomorrow.
> Is it even clear why numerous archives aren't hosted on PyPI?
No, the only one that has mentioned why is Marc-André, I think, whose
eGenix packages are distributed as binary packages for loads of
different platforms. It's unclear to me if all these binary packages
should be uploaded to PyPI, and it is also unclear to me why they
can't be, it seems to be mostly a case of it being too much work.
He also mentioned the big Python distributions eGenix does as being
too large for PyPI, but I don't really see the point of uploading
Python distributions to PyPI, they can't be installed with Python
> IMHO it would be better to remove barriers than force projects to host files on PyPI.
Nobody has really been able to point out any real barriers, so we
don't know what they are or if they exist.
More information about the Catalog-SIG