Hi,<br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 30, 2012 at 11:52 PM, Brett Cannon <span dir="ltr"><<a href="mailto:brett@python.org" target="_blank">brett@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="gmail_extra"><div class="gmail_quote"><div class="im">On Fri, Nov 30, 2012 at 4:07 PM, R. David Murray <span dir="ltr"><<a href="mailto:rdmurray@bitdance.com" target="_blank">rdmurray@bitdance.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>On Fri, 30 Nov 2012 14:38:12 -0500, Brett Cannon <<a href="mailto:brett@python.org" target="_blank">brett@python.org</a>> wrote:<br>
> Do we have a graph of the historical trend of the number of bugs (or at<br>
> least the historical details stored somewhere)? I think we have had a net<br>
<br>
</div>Not really. Ezio made one by hand once, but there is nothing automated.<br></blockquote></div></div></div></blockquote><div><br>The one I made can be found here: <a href="https://docs.google.com/spreadsheet/ccc?key=0AplyAWXqkvHUdFF0SkVrT3VKcnRBZXNrR1hleHowWnc">https://docs.google.com/spreadsheet/ccc?key=0AplyAWXqkvHUdFF0SkVrT3VKcnRBZXNrR1hleHowWnc</a><br>
I now updated it with the latest data.<br>On the Sheet 2 you can find additional graphs that show the releases of Python together with the data. Only final releases are included, alphas, betas and rcs are not included.<br>
The spreadsheet is a bit messy because I was experimenting with different kind of graphs and trying to work around some limitations of Google Docs, but it should be good enough.<br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="gmail_extra"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
The historical details are stored only in the mailing list archives, as<br>
far as I know. In theory I think you could re-calculate them from the<br>
Roundup DB, but for various reasons the numbers would probably come out<br>
slightly different. Still, getting the data from the DB would be better<br>
than parsing the emails, since for one reason and another there are<br>
missing Friday reports, and reports that were issued on non-Friday<br>
dates.<br></blockquote></div></div></div></blockquote><div><br>One option I was considering is having the weekly report script append the result on a file and make it available on <a href="http://bugs.python.org">bugs.python.org</a>, or even use it to generate graphs directly. This is something I considered and planned to implement for a long time, but haven't done it yet.<br>
<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_extra"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><br>
> decrease in open bugs the last couple of weeks and it would be neat to see<br>
> an absolute and relative graph of the overall trend since Python 3.3.0 was<br>
> released. Also might make a nice motivator to try to close issues faster. =)<br>
><br>
> Otherwise is the code public for this somewhere? I assume it's making an<br>
<br>
</div>Yes. It is in the software repository for our roundup instances:<br>
<br>
<a href="http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary" target="_blank">http://hg.python.org/tracker/python-dev/file/default/scripts/roundup-summary</a><br>
<br>
(Be warned that that isn't the location from which the script is<br>
executed, so it is possible for what is actually running to get out of<br>
sync with what is checked in at that location.)<br>
<div><br>
> XML-RPC call or something every week to get the results, but if I decide to<br>
<br>
</div>Nope, it talks directly to the DB. And as you will see, it is more<br>
than a bit gnarly.<br>
<div><br></div></blockquote><div><br></div></div><div>I think I could also download the csv file and parse that to get whatever data I wanted.<br></div></div></div></blockquote><div><br>To figure out when an issue was closed you need to access its history, and that's not available through XML-RPC/csv IIRC. You should be able to figure out when the issue got created though.<br>
Anyway, it's probably easier to implement something like what I mentioned earlier.<br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="gmail_extra"><div class="gmail_quote"><div></div><div class="im"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
> do a little App Engine app to store historical data and do a graph I would<br>
> rather not have to figure all of this out from scratch. =) Although I could<br>
> I guess also parse the email if I wanted to ignore all other emails.<br>
<br>
</div>I'm not sure how one would go about integrating the above with an App<br>
Engine app. I suspect that not quite enough information is available<br>
through the XML-RPC interface to replicate that script, but maybe you<br>
could manage just the open-close counting part of it. I haven't<br>
looked at what it would take.<br></blockquote><div><br></div></div><div>It really depends on what statistics I cared about (e.g. there are less than 4000 bugs while there are less than 25,000 closed bugs). If I just did high-level statistics it wouldn't be bad, but if I try to track every issue independently that might be annoying (and actually cost money for me, although I already personally pay for <a href="http://py3ksupport.appspot.com" target="_blank">py3ksupport.appspot.com</a> so I can probably piggyback off of that app's quota). We will see if this ever goes anywhere. =)<br>
</div></div></div>
<br></blockquote></div><br>Another somehow related project/experiment I've been working on is collecting stats about the patches available on the tracker. I put together a temporary page that allows you to enter the name of a module (or any file/path) and get a list of issues with patches that affect the specified module(s): <a href="http://wolfprojects.altervista.org/issues.html">http://wolfprojects.altervista.org/issues.html</a><br>
FTR this is based on the word done by anatoly (see links on the page).<br>I'm planning to eventually integrate this in the tracker too, but lately I don't have too much time, so there's no ETA.<br><br>Best Regards,<br>
Ezio Melotti<br></div>