[Python-Dev] Summary of Python tracker Issues

"Martin v. Löwis" martin at v.loewis.de
Sat Sep 25 14:10:47 CEST 2010

>> 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.

The total numbers reported are really the totals. Also, the delta
reported for the totals is the difference to the last report.

The number reported with +/- for open/closed are *not* deltas, but the
number of issues opened since last week. As some open issues were closed
and some closed issues were opened, they don't sum up the way you
expect. An example:

  open:   #1 #2
  closed: #3 #4
  open:   #1 #3 #5
  closed: #2 #4

The report would be

  open: 3 (+2, namely #3 and #5); delta would be +1
  closed: 2 (+1, namely #4); delta would be 0

IOW, the numbers after +/- match the counts in the lists shown below,
not the delta since last week.


More information about the Python-Dev mailing list