Re:Pypants (Django Dash 2009)
by duke_sam on Monday June 01, 2009 @09:29AM
(#636033)
It was part of the Django Dash so the guys only had 2 days to build it, hence the scaling issues :D. AFAIK they are continuing work on it (add support for SVN/HG etc.) so stability should improve pretty fast.
Re:Pypants (Django Dash 2009)
by run4yourlives on Monday June 01, 2009 @02:00PM
(#636463)
Grading on what though?
Number of lines of code? Size of methods? Number of commits? How much you like them?
An about page with the grading methodology should probably be the next thing you publish. Also, in my mind the historical breakdown is irrelevant. I couldn't care less if the project sucked two weeks ago if they re-factored and are now "a" quality. Of course, that's if I knew what "A" quality meant. :-)
Other than that, not a bad effort for a dash project. It's a neat idea and something that could prove very useful.
Re:Pypants (Django Dash 2009)
by duke_sam on Monday June 01, 2009 @04:02PM
(#636676)
Well I'd be more likely to use a piece of code if I see that people have constant commits that are raising the quality of the code base. At least this way you aren't just going by commits/releases, you get to see how they changed the quality of the product.
http://pypants.org/projects/amqplib/0.6/evaluations/226/
It only works for python packages currently. You can point it at any git repository that has a python package in it (watch the screencast).
Number of lines of code? Size of methods? Number of commits? How much you like them?
An about page with the grading methodology should probably be the next thing you publish. Also, in my mind the historical breakdown is irrelevant. I couldn't care less if the project sucked two weeks ago if they re-factored and are now "a" quality. Of course, that's if I knew what "A" quality meant. :-)
Other than that, not a bad effort for a dash project. It's a neat idea and something that could prove very useful.