[Python-Dev] Automated testing of patches from bugs.python.org
techtonik at gmail.com
Wed May 20 09:44:13 CEST 2015
On Tue, May 19, 2015 at 11:37 PM, Terry Reedy <tjreedy at udel.edu> wrote:
> On 5/19/2015 11:02 AM, Kushal Das wrote:
>> With the help of CentOS project I am happy to announce an automated
>> system  to test patches from bugs.python.org. This can be fully
>> to test the patches whenever someone uploads a patch in the roundup, but
>> for now it accepts IRC commands on #python-dev channel. I worked on a
>> docker based prototype during sprints in PyCon.
>> How to use it?
>> 1. Join #python-dev on irc.freenode.net.
>> 2. Ask for test privilege from any one of kushal,Taggnostr,bitdancer
>> 3. They will issue a simple command. #add: YOUR_NICK_NAME
>> 4. You can then test by issuing the following command in the channel:
>> #test: BUGNUMBER
>> like #test: 21271
> What if there are multiple patches on the issue? Pick the latest?
> This is not correct if someone follows up a patch with a 2.7 backport, or if
> there are competing patches.
Here is the code that checks how much outstanding patches a certain
module has by downloading all patches from open issues, parsing them
and comparing the paths. It is possible to reuse the parser to check paths
in patch against paths present in certain Python versions, or add different
All this is pure Python and should work cross-platform too.
This was intended to add status for bugs.python.org, but the work on
Roundup had stalled due to uncertainty and despair on how to handle
utf-8 (internal to Roundup) vs unicode (internal to Jinja2) in this issue:
The root of the problem is that Python 2.7 uses 'ascii' and not 'utf-8'
internally, so Jinja2 engine fails with 'ascii' ordinal not in range
somewhere in the way. Need an expert advice how to handle that, because
my brain power is not enough to process it.
More information about the Python-Dev