Both Homer and the IssueTrackerProduct is getting fat Yesterday I released the IssueTrackerProduct 0.6.9 and after having done that I took a quick LOC count: 10,038 lines of Python code!

That has taken me well over two years but I think most of it has been written in the last year actually. Since the 0.5.2 release (first release on www.issuetrackerproduct.com) it has grown by about 11 lines per day (from 4,000 loc since 11 Dec 2004).

I don't know what to make of this. One must remember that almost 100% of the code is written by me and only the python code is include (there is 8,500 lines of template code excluded). Lines of code is a pretty poor measure of anything because it so dearly matters how a program is written. The CSS lib that decrypts a DVD, isn't that less than 10 lines of code? RT and Bugzilla weigh in at 23,000 and 26,000 lines of Perl code for example.

Compared to some "competing" bug/issue tracker systems written in Python, the IssueTrackerProduct is currently the biggest:

IssueTrackerProduct 10,038
Edgewall Trac 9,470
IssueDealer 6,929
PloneCollectorNG 4,826
Roundup 658

mazid - 03 August 2010 [«« Reply to this]
cool, i dont know python, it might be my next target.
any way i was googling for 10000 loc !
just after finiching my web application (php based) with 10321 loc in 5 months...
including learning php, js and mysql :)


Your email will never ever be published