Thanks for this, Louie! Definitely interesting to look at what modules have the most open patches against them (spoiler alert: it's apparently argparse with 51).
On Tue, 25 Apr 2017 at 22:18 Louie Lu <m...@louie.lu> wrote: > Hi all, > > Fix some pr counting issue, and now the bpo-mergerate can choose hg (the > old process), git, or all for mergerate counting. Also, relative bpo issue > can be expand by clicking row for more detail. > > demo site: https://bpo-mergerate.louie.lu > > Best Regards, > Louie. > > 2017-04-25 16:18 GMT+08:00 Louie Lu <m...@louie.lu>: > >> Hi all, >> >> Current merge rate is count in a mixed way (patch + PR). >> >> After reading Bertt's post "The history behind the decision to move >> Python to GitHub", I would like to separate the count of merge rate to hg >> and GitHub. >> >> It may check that did migrate to GitHub get the better process of CPython >> development. >> >> >> Best Regards, >> Louie. >> >> >> >> 2017-04-24 23:55 GMT+08:00 Louie Lu <m...@louie.lu>: >> >>> Hi all, >>> >>> thanks for all your reply, since roundup didn't contain JSON REST API, >>> and I'm not sure did roundup robot have deal with "patched but still open" >>> situation, thus I do some change to bpo-mergerate and have some result. >>> >>> GitHub repo: https://github.com/lulouie/bpo-mergerate >>> Demo site: https://bpo-mergerate.louie.lu >>> >>> Now bpo-mergerate using SQLite database and no more CSV file, and an >>> update.py script was added, on my host, it will automatically update the >>> bpo patch status hourly. >>> For the site, it is now using ajax and can deal with fuzzy search. >>> >>> The merge rate calculate is now find-grained to per-file, and will >>> automatically count the prefix merge rate, for example: >>> >>> Searching: Lib/test >>> Result: >>> path merged open total rate >>> /Lib/test 3013 1359 4372 68.916 >>> Lib/test/test_ssl.py 60 15 75 80.000 >>> Lib/test/test_inspect.py 56 12 68 82.353 >>> >>> >>> I think the site function is complete now, welcome for any suggestion. >>> (maybe like speed.python.org make a timeline for the merge rate?) >>> >>> Best Regards, >>> Louie. >>> >>> 2017-04-24 12:08 GMT+08:00 Nick Coghlan <ncogh...@gmail.com>: >>> >>>> On 21 April 2017 at 06:04, Wes Turner <wes.tur...@gmail.com> wrote: >>>> > 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 >>>> >>>> There's also a pending patch to add a HTTPS+JSON REST API to our >>>> Roundup instance: >>>> http://psf.upfronthosting.co.za/roundup/meta/issue581 >>>> >>>> Definite +1 for the general idea of collecting and publishing these >>>> kinds of statistics, though - I can see them being quite useful to a >>>> variety of audiences. >>>> >>>> Cheers, >>>> Nick. >>>> >>>> P.S. The upstream Roundup project is also interested in offering that >>>> capability by default: http://issues.roundup-tracker.org/issue2550734 >>>> >>>> -- >>>> Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia >>>> >>> >>> >> > _______________________________________________ > 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 >
_______________________________________________ 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/archive%40mail-archive.com