[Tracker-discuss] [Python-Dev] Summary of Python tracker Issues
ajaksu at gmail.com
Wed May 6 09:11:58 CEST 2009
Daniel Diniz wrote:
R. David Murray wrote:
>> I suggest we change
>> this report to provide statistics that are designed to encourage people
>> using the tracker when they make progress on reducing the total number
>> of outstanding bugs, or at least make it clear that the open bug count
>> isn't increasing as fast as the above report format makes it seem.
> I'll try to implement this today.
It took me a couple of days just to understand how the report is generated :/
A refactored version of roundup-summary is attached, you can compare
its ugly code to the original ugly code at
- Pass arguments to functions instead of having everything as globals.
- Simplify table template parsing and result generation, avoiding eval()s.
- Replace lots of print-based output with a few .write() calls.
- Move code from module scope into (many!) functions.
- Merge similar functions/classes, split long functions into smaller ones.
- Fix spaces/tabs, long lines, variable and function naming, unused imports.
- Miscellaneous reorganization.
It's supposed to be a drop-in replacement to the current
roundup-summary, but its output has a couple spurious whitespaces
compared to the original's.
I have to let this rest for at least another week, but I'll be able to
add your suggested report format after that.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 34721 bytes
Desc: not available
More information about the Tracker-discuss