[Catalog-sig] Package Quality Measurement for packages on Pypi

David Lyon david.lyon at preisshare.net
Fri Nov 20 03:25:50 CET 2009

Hi Srid,

On Thu, 19 Nov 2009 12:11:01 -0800, "Sridhar Ratnakumar"
<sridharr at activestate.com> wrote:
> I agree about metadata (not sure about documentation). Based on what I
>  from building packages[1] for PyPM, most packages fail due to one of the
> following reasons:
> 1) Missing PKG-INFO file (the author did not use the `sdist` command).  
> Twisted, IMDBPy are some examples.
> 2) Trying to read a non-existent file from setup.py (eg: author forgot to
> include README.txt in the tarball -- buggy MANIFEST.in?)
> 3) no setup.py
> 4) reading stdin in setup.py (so the "setup.py build" runs indefinitely)
> 5) no downloads URL (no tarballs either)
> 7) Import itself in setup.py (foo-0.1.tar.gz/setup.py has "import foo" --
> and that in turns imports uninstalled deps)
> 6) Missing "build dependencies" (many packages try to import  
> numpy.distutils/twisted so on)
> Other failures usually include missing library dependencies (libxml, for 

> instance) or some Python syntax error.

So what do you guys do with the results?


More information about the Catalog-SIG mailing list