[Python-Dev] Summary of Python tracker Issues

Georg Brandl g.brandl at gmx.net
Sat Sep 25 13:11:41 CEST 2010

Am 25.09.2010 03:45, schrieb Brett Cannon:
> On Fri, Sep 24, 2010 at 13:04, Georg Brandl <g.brandl at gmx.net> wrote:
>> So by opening and closing a bug 5 times within a week, the "open" and
>> "close" counters both go up by 5?  That would be stupid.
> No, as in a bug was re-opened last week and then closed again this week.
>> Issues can't be open and closed at the same time.  There is a count of
>> open issues at the start of the week, and one at the end of the week.
>> There's a difference between those two counts which in total must sum
>> up to the total difference in issues.
>> If I understand correctly how the counters work, they at least need to
>> be renamed -- they do *not* count open/closed issues, they count
>> openings/closings.
> Guess the only way to settle this is look at the code, but I don't
> care enough to bother. =)

I'll bother Ezio when he's back.  It just feels strange to me that the bit
of statistic I feel is most interesting -- whether there are less open bugs
at the end of the week than at the start -- is not obvious from the report.


Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent thou
two, excepting that thou then proceed to four. Tabs are right out.

More information about the Python-Dev mailing list