Leo Famulari skribis:
> On Sun, Jan 03, 2016 at 03:18:23PM +0100, Ludovic Courtès wrote:
>> Leo Famulari skribis:
>>
>> > On Thu, Dec 10, 2015 at 02:05:56AM -0500, Leo Famulari wrote:
>> >> python-urwid-1.3.0 fails to build on x86_64 during the
>> >> "AsyncioEventLoopTest" test with the error "
On Sun, Jan 03, 2016 at 03:18:23PM +0100, Ludovic Courtès wrote:
> Leo Famulari skribis:
>
> > On Thu, Dec 10, 2015 at 02:05:56AM -0500, Leo Famulari wrote:
> >> python-urwid-1.3.0 fails to build on x86_64 during the
> >> "AsyncioEventLoopTest" test with the error "KeyError: '5 is not
> >> regist
Leo Famulari skribis:
> On Thu, Dec 10, 2015 at 02:05:56AM -0500, Leo Famulari wrote:
>> python-urwid-1.3.0 fails to build on x86_64 during the
>> "AsyncioEventLoopTest" test with the error "KeyError: '5 is not
>> registered'". It has failed repeatedly for some time now. It fails in
>> the same w
On Thu, Dec 10, 2015 at 02:05:56AM -0500, Leo Famulari wrote:
> python-urwid-1.3.0 fails to build on x86_64 during the
> "AsyncioEventLoopTest" test with the error "KeyError: '5 is not
> registered'". It has failed repeatedly for some time now. It fails in
> the same way when updated to python-urwi
On Thu, Dec 10, 2015 at 02:05:56AM -0500, Leo Famulari wrote:
> python-urwid-1.3.0 fails to build on x86_64 during the
> "AsyncioEventLoopTest" test with the error "KeyError: '5 is not
> registered'". It has failed repeatedly for some time now. It fails in
> the same way when updated to python-urwi
python-urwid-1.3.0 fails to build on x86_64 during the
"AsyncioEventLoopTest" test with the error "KeyError: '5 is not
registered'". It has failed repeatedly for some time now. It fails in
the same way when updated to python-urwid-1.3.1.
I looked for interesting changes made between the last succe
