Roundup has an xmlrpc API: 

- https://sourceforge.net/p/roundup/code/ci/default/tree/roundup/xmlrpc.py
- https://sourceforge.net/p/roundup/code/ci/default/tree/test/test_xmlrpc.py


http://roundup.sourceforge.net
https://sourceforge.net/p/roundup/code/

Tangentially, here's a PR to add gh pr http webhook support to Roundup:

https://github.com/AnishShah/roundup/commit/84cdf84946835c883a1384c4ece649355f7e7669

April 19, 2017, Louie Lu <me@louie.lu> wrote:
I used the download CSV function, and make some change about it.

The demo of the site is here:

    https://bpo-mergerate.louie.lu/


To used, just need to enter the prefix of dictionary to search bar, for now, its resolution is to the second folder or files, e.g., Lib/unittest, Python/ceval.c


This searches files changed in issue patch attachments or more like e.g. `git log Lib/unittest` `git blame Lib/unittest`?
 
 

2017-04-20 5:04 GMT+08:00 Brett Cannon <brett@python.org>:
I don't think there's any API. Your best bet will probably be to analyze the GitHub data.

On Tue, 18 Apr 2017 at 09:09 Louie Lu <me@louie.lu> wrote:
Hi all,

After reading some topic at python-committers mailing list, some of the topics are around not enough reviewers to review patches, cause the develop process slowing down or the patch can't merge into the codebase.

I would like to make some analysis about module / library patch merge rate (maybe fine-grained to per file?), and make a statistic list that can point out which module / library need more people to contribute to it.

Are there any API for bugs.python.org can be used, or there is a existing thing just doing what I want to do. (Or maybe Python tracker, who sent the summary can add this kind of function.)

Thanks,
Louie.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: https://mail.python.org/mailman/options/python-dev/brett%40python.org