[Catalog-sig] Proposal: Move PyPI static data to the cloud for better availability (version 2)

Ian Bicking ianb at colorstudy.com
Tue Jun 29 23:39:11 CEST 2010

On Tue, Jun 29, 2010 at 4:22 PM, "Martin v. Löwis" <martin at v.loewis.de>wrote:

> > I'm surprised, what specific mod_wsgi configuration did you try?
> Not sure I understand the question:
> WSGIDaemonProcess pypi display-name=wsgi-pypi processes=10 threads=1
> maximum-requests=2000
> WSGIProcessGroup pypi
> WSGIPassAuthorization On
> WSGIScriptAlias /pypi /data/pypi/src/pypi/pypi.wsgi
> WSGIScriptAlias /simple /data/pypi/src/pypi/pypi.wsgi
> According to the bzr log, I reverted that because Python would crash
> (with a core dump).

OK, that's how I would configure it too.  A core dump implies some
installation problem (e.g., mod_wsgi was compiled against one version of
Python, but is being bound to a different version -- or psycopg or some
other extension).  Graham Dumpleton is very responsive about these kinds of
issues with mod_wsgi if you mail the mod_wsgi list; I've always stuck to
debs and that's saved me from version mismatches, so I haven't actually
debugged issues like this myself.

Ian Bicking  |  http://blog.ianbicking.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/catalog-sig/attachments/20100629/dec8da62/attachment.html>

More information about the Catalog-SIG mailing list