Since mercurial makes me annoyed I decided to use it. I'll have to learn it someday anyway, so why not now?
https://bitbucket.org/regebro/pyroma Helpers welcome (although you'll probably have to wait to after PyCon). //Lennart On Sun, Mar 6, 2011 at 20:40, Lennart Regebro <rege...@gmail.com> wrote: > The winner is Wichert, with "pyroma". > > I do like the "stickler" name, and the cheeseshop namespace, but since > there is nothing else in that namespace I'll wait with it. It can > easily be moved to a "cheeseshop.compliance" or whatever in the > future, but that the moment it's "pyroma". I'll check it in somewhere > soon, maybe work a bit more on the plane to PyCon and probably mention > it in a lightning talk. > > > //Lennart > > On Sun, Mar 6, 2011 at 09:46, Lennart Regebro <rege...@gmail.com> wrote: >> I've started working on a little utility to give a quality rating on >> packages, expressed in 0-10 points, and also in cheese types, >> according to smellyness. >> >> It's going to check for things like that it has all meta data it >> should have, such as author_email, specifies Python versions via the >> trove classifiers (currently works) and that it specifies all >> dependencies (still todo). It will support both checking on a package >> (works currently) a distribution file and PyPI (still to do). >> >> It's not a uniqe idea, it overlaps with Andreas Jungs >> zopyx.trashfinder in scope, and it will also in the case of checking a >> package on PyPI check that there are several people that have owner >> access, and hence include the functionality of mr.parker. (In fact >> when checking on PyPI it will also check if there are documentation on >> packages.python.org, that the distribution files are uploaded to PyPI, >> etc, but this is all still todo). But I didn't find anything else, and >> I wanted bigger scopes than both these in what to check in and which >> cases. >> >> But, before I move this to a public repository and upload it to PyPI, >> there is one important thing to be determined: What should it be >> called? Currently I'm calling it "pypilib.quality". I don't mind this >> kind of boring names, but there is currently not a pypilib namespace, >> and I don't want to just create top level namespaces left and right >> for no reason. So other names are welcome. It doesn't have to have a >> namespace either. >> >> In the long run I would not mind to see this utility integrated into a >> general pypi/cheeseshop script with other utility commands, which even >> could include installing and removing, thusly giving Perl people what >> they think they want a "CPAN" for Python. :-) >> >> -- >> Lennart Regebro: http://regebro.wordpress.com/ >> The Python 3 Porting book is out: http://python3porting.com/ >> +33 661 58 14 64 >> > _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
