[Python-Dev] Patchs and bugs resume

Brett Cannon brett at python.org
Tue Mar 20 23:10:25 CET 2007

On 3/20/07, Facundo Batista <facundo at taniquetil.com.ar> wrote:
> People:
> At the beginning of March, there was a thread in this list about patchs
> and bugs that teorically weren't checked out.
> >From that discussion, I asked myself: "How can I know the temporal
> location of a patch/bug?". Are there a lot of old patchs/bugs? Those
> that are old, don't have any update or there're a big discussion with
> each one? Are they abandoned?
> To help me with this analisys, I made a tool that taking information
> from SourceForge it creates a resume table, for the patchs...
>   http://www.taniquetil.com.ar/facundo/py_patchs.html
> ...and the bugs:
>   http://www.taniquetil.com.ar/facundo/py_bugs.html
> My idea is to update them periodically (something like each day, at
> the end of the html you have the update date and time).

That's some interesting stuff.  Took me a second to realize that the
temporal column's total length is the time range from the opening of
the oldest bug to the latest comment made on any bug and that the blue
bar is where within that time frame the bug was opened and the last
comment was made on that bug.

But still interesting!  Led to me closing a bug and a patch that were
old and had not been touched in ages.  Hopefully you will be able to
easily port this over to the new tracker once it's up (that should
happen 2-4 weeks after 2.5.1 is released).


More information about the Python-Dev mailing list