Re: [Python-Dev] Patchs and bugs resume
Martin v. Löwis wrote: When you do, make sure you take a look at roundup's search facilities. Roundup keeps a 'last activity' field, on which you can search and sort, and a 'creation date' field (likewise). Could you please point me to documentation about the new tracker? I want to study the best way to extract information from it (right now, I'm just pulling htmls from SF and parsing them, and that's not easy, fast, nor clean). Thank you! -- . Facundo . Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Patchs and bugs resume
Could you please point me to documentation about the new tracker? I want to study the best way to extract information from it (right now, I'm just pulling htmls from SF and parsing them, and that's not easy, fast, nor clean). The tracker software is roundup. It's documentation is at http://roundup.sourceforge.net/ However, I suggest that you just create/recover your account at bugs.python.org (recover using your SF account name), then go to Search, customize a search, perform it, and look at the 'Download as CSV' link. HTH, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Patchs and bugs resume
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). You can be sure I'll port it... When you do, make sure you take a look at roundup's search facilities. Roundup keeps a 'last activity' field, on which you can search and sort, and a 'creation date' field (likewise). Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Patchs and bugs resume
| On 3/20/07, Facundo Batista [EMAIL PROTECTED] wrote: | Brett Cannon wrote: | 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). | | You can be sure I'll port it... I am a fan of Edward Tufte and his advocacy of graceful mixtures of text and small graphics. I think this is an example. A possible improvement, if possible, would be to use thin dark bars for actions (comments) and a lighter bars for periods of inactivity. This would differentiate between items that have had no comments between first and last and those with several. tjr ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Patchs and bugs resume
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). Enjoy it. Regards, -- . Facundo . Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Patchs and bugs resume
On 3/20/07, Facundo Batista [EMAIL PROTECTED] 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). -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Patchs and bugs resume
Brett Cannon wrote: 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. M, you're right, I should have explained it somewhere... 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). You can be sure I'll port it... -- . Facundo . Blog: http://www.taniquetil.com.ar/plog/ PyAr: http://www.python.org/ar/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Patchs and bugs resume
On 3/20/07, Facundo Batista [EMAIL PROTECTED] wrote: Brett Cannon wrote: 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. M, you're right, I should have explained it somewhere... 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). You can be sure I'll port it... Great! It already led to me closing four bugs, another waiting for people to not speak up, and a sixth for me to fix! -Brett ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
