[Catalog-sig] Package Quality Measurement for packages on Pypi
sridharr at activestate.com
Fri Nov 20 03:50:16 CET 2009
On Thu, 19 Nov 2009 18:25:50 -0800, David Lyon <david.lyon at preisshare.net>
> 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 for PyPM, most packages fail due to one of
>> 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
>> 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?
Can you elaborate your question?
More information about the Catalog-SIG