On Mon, 29 Jun 2009 18:52:01 -0700, P.J. Eby <pje@telecommunity.com> wrote:
The thing is, there is a source distribution of Pyro right there on the SourceForge website. Why doesn't this grab the .tar.gz file and build and install it? I thought setuptools did this automatically. Perhaps my memory is failing me. (It wouldn't be the first time.) Two things. First, the correct URL for Pyro downloads is http://sourceforge.net/project/showfiles.php?group_id=18837&package_id=29259 . Second, Sourceforge has changed their pages again so that they no longer give direct links to downloadable files; instead, they link to a "downloading.php" which setuptools does not recognize as a downloadable file. I'm not sure when this changed on Sourceforge, but I do hope that SF users will complain long and loud about it.
Just throwing out some ideas: Wouldn't it be better for package authors to register their packages in PYPI? They don't have to upload the entire tarball .. but even giving a /direct link/ to this would be sufficient. Would providing pypi plugin that uploads sdist's to SourceForge (or freshmeat, so on) make this process easier for package authors? Maybe then the network effect will make setuptools not rely too much on the unreliable download logic .. as eventually most SF packages would have a download link on PyPI for every subsequent release. -srid