[Python-ideas] A tuple of various Python suggestions

[Nick Coghlan]

On 11 April 2016 at 18:56, Chris Angelico <rosuav at gmail.com> wrote:
> On Mon, Apr 11, 2016 at 6:51 PM, Nick Coghlan <ncoghlan at gmail.com> wrote:
>> Many of the oldest issues remain open because they're rare, easily
>> worked around, hard to fix, only arguably a bug, or some combination
>> of the above. Even reviewing them to see if they're still valid can be
>> time consuming.
>
> Maybe this is where someone like Keith can contribute? Go through a
> lot of old issues and inevitably there'll be some that you can
> reproduce with the version of Python that was current then, but can't
> repro with today's Python, and they can be closed as fixed. Doesn't
> take any knowledge of C, and maybe not even of Python (if there's a
> good enough test case there).

+1

As David Murray has pointed out on occasion, browsing through the
tracker "oldest first" can also be interesting in terms of reading the
discussions and seeing what leads to issues remaining open for a long
time.

Separating out "Open Enhancements" as a subcategory of "Open Issues"
is also a longstanding "nice-to-have" for the metrics collection - the
script for the weekly data collection is at
https://hg.python.org/tracker/python-dev/file/tip/scripts/roundup-summary
, while https://hg.python.org/tracker/python-dev/file/tip/scripts/issuestats.py
pulls the time series created by those notifications and turns it into
a chart.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia