[Python-Dev] Summary of Python tracker Issues (original) (raw)

R. David Murray rdmurray at bitdance.com
Tue Aug 10 17:02:48 CEST 2010

On Tue, 10 Aug 2010 17:28:18 +0300, Ezio Melotti <ezio.melotti at gmail.com> wrote:

Hi, lately I've been working on the new summary of Python tracker issues. This is the result.

Thanks for working on this, Ezio!

> Issues stats: > open 2640 (+35) > closed 18679 (+194) > total 21319 (+57)

The +35 means that there are 35 more issues opened since the last week. This is not the number of issues that have been created during the last week, but the number of new issues that have been created or reopened that are still open. Also note that 'pending' and 'languishing' are considered as 'open' too.

How about changing the label to 'not closed' to make that clear?

> Issues opened (35) > ================== > > #8821: Range check on unicode repr > http://bugs.python.org/issue8821 reopened by pitrou > [...]

This is the list of all the issues created or reopened during the last week that are still open.

I wonder if it would be useful to split this into two tables, one for new issues still open and one for reopened issues. I think the mental space in which one considers re-opened issues is different from the one for new issues. In particular, a developer who doesn't have time to scan the new issues might notice a reopened issue they were involved in but haven't yet looked at their 'nosy' email about. Perhaps not worth the effort, it's just a thought.

> Recent issues with no replies (15) > ================================== > > #9535: Pending signals are inherited by child processes > http://bugs.python.org/issue9535 > [...]

This is the list of the open issues with only 1 message, sorted by creation date. The list is limited to max 15 issues but is not limited to the last week. This means that issues older than a week are included here if less than 15 issues with only 1 message have been created this week. > Issues waiting for review (15) > ============================== > > #1474680: pickling files works with protocol=2. > http://bugs.python.org/issue1474680 > [...] This is the list of issues with 'patch' or 'needs review' keywords or 'patch review' stage that have been active during the last week. The list is limited to max 15 issues.

For both of these I think it is important that the fact that they are limited to 15 be mentioned in the section header.

The issues needing review is a great addition, probably every bit as valuable as the no replies report. I hope that it, too, will draw on the previous weeks if there are less than fifteen that were active in the current week?

> Top issues most discussed (10) > ============================== > > #9079: Make gettimeofday available in time module > http://bugs.python.org/issue9079 42 msgs > [...]

This is the list of issues with activity in the last week sorted by number of message. This list is limited to max 10 issues.

I've already talked with Ezio in IRC about the fact that this list represents a regression from the old report, since the old report gave the issues with the most messages during the week whereas his current looks at the total message count for any issue that has had any activity during the current week. He's going to fix that.

> Issues closed (154) > =================== > > #1474680: pickling files works with protocol=2. > http://bugs.python.org/issue1474680 closed by alexandre.vassalotti > [...]

This is the list of all the issues closed in the last week *that are still closed*. Since this list might be quite long I put it at the end, to make it easier to reach the other lists.

It would be lovely if we could manage to get this one to be the longest table in the report each week :)

-- R. David Murray www.bitdance.com

More information about the Python-Dev mailing list