One of our products uses pycassa. The product is built with zc.buildout v1. zc.buildout uses another package (i think easy_install) to get pycassa.
The page https://pypi.python.org/simple/pycassa/ is somehow automatically found by easy_install and rather than just downloading the tarball listed on that page it goes for the "download url", which now does not work. The download url for the latest version is http://github.com/downloads/pycassa/pycassa/pycassa-1.8.0-1.tar.gz which does not work, it gives a 404
Sorry to use the email list to report this but I could not find a place to report this directly to
Thanks
--
Jamie
--
You received this message because you are subscribed to the Google Groups "pycassa-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pycassa-discu...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
The url still gives me a 404
(https://github.com/downloads/pycassa/pycassa/pycassa-1.8.0-1.tar.gz).
Considering that github is discontinuing its download service and has
stopped accepting new files, this is kind of expected.
Hanno
Why are we using download_url at all? Since the tarball is already
hosted on pypi and its mirrors?
Hanno
Both easy_install and pip prefer to follow the download_url if it is
set (last I checked).
But the general consensus is to avoid hosting on external services, as
these just add an extra source of risk and unreliability to the
system. github, sourceforge or Google code all suffer from downtimes -
far more often than you'd expect. pypi has a couple of geographically
distributed mirrors by now and pip/easy_install/buildout can use
those.
So I'd suggest we remove the download_url for the next release.