Can you submit a bug at bugs.python.org?
The minimal example I found:
>>> class a(int): pass
...
>>> for i in range(0, a(5)): pass
...
Traceback (most recent call last):
File "", line 1, in
SystemError: Objects/longobject.c:400: bad argument to internal function
>>>
On Dec 19, 2007 5:38 PM,
On Wed, Dec 19, 2007 at 05:58:35PM -0800, Brett Cannon wrote:
-> On Dec 19, 2007 4:33 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
-> > The bots are kicking-off so many false alarms that it is becoming
difficult to tell whether a check-in genuinely broke a build.
-> >
-> > At the root of the p
On Dec 19, 2007 4:33 PM, Raymond Hettinger <[EMAIL PROTECTED]> wrote:
> The bots are kicking-off so many false alarms that it is becoming difficult
> to tell whether a check-in genuinely broke a build.
>
> At the root of the problem is a number of tests in the test suite that
> randomly blow-up.
All,
I posted this up to comp.lang.python earlier today and asked a few questions
around IRC. The general consensus appeared to be that this was a bug. Before
opening up an issue on it, I wanted to run it by this list first (just in case)
Here is a copy / paste from comp.lang.python:
URL:
The bots are kicking-off so many false alarms that it is becoming difficult to
tell whether a check-in genuinely broke a build.
At the root of the problem is a number of tests in the test suite that randomly
blow-up. I now tend to automatically dismiss failures in test_logging and
test_threadi
