[Python-bugs-list] [ python-Bugs-676155 ] RuntimeWarning with tp_compare

[SourceForge.net]

Bugs item #676155, was opened at 2003-01-28 10:55
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=676155&group_id=5470

Category: None
Group: None
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Andrew Dalke (dalke)
>Assigned to: Nobody/Anonymous (nobody)
Summary: RuntimeWarning with tp_compare

Initial Comment:
>From the latest CVS, as of the morning of Jan. 28 2003

>>> s = "12345" * 1000
>>> float(s) == int(s)
__main__:1: RuntimeWarning: tp_compare didn't return -1
or -2 for exception
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
OverflowError: long int too large to convert to float
>>>



----------------------------------------------------------------------

>Comment By: Neal Norwitz (nnorwitz)
Date: 2003-01-28 12:41

Message:
Logged In: YES 
user_id=33168

Let me try that again, this time without confusing the
issues.  Sorry about that.

The patch does fix the coerce problem I mentioned.

The patch also fixes the bug report problem in that now an
OverflowError is raised.  However, even with the patch I get
the undetected error:

>>> float(s) == int(s)
False
XXX undetected error
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
OverflowError: long int too large to convert to float

I'll keep working on the problem.  Should be pretty shallow
now, I hope.

----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2003-01-28 12:33

Message:
Logged In: YES 
user_id=6656

That looks like the fix to me.

Presumably you meant "*without* this patch I get..."?

I suggest you check it in.

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2003-01-28 12:23

Message:
Logged In: YES 
user_id=33168

I thought I fixed the problem in one place (patch attached).
 That fixes this problem:

 coerce(0.5, int(s))

With this patch, I get:
XXX undetected error (why=3)


----------------------------------------------------------------------

Comment By: Michael Hudson (mwh)
Date: 2003-01-28 12:15

Message:
Logged In: YES 
user_id=6656

Hmm, wierd.  I think there may be a case of something
setting an exception and then not returning NULL (or
whatever).  You can certainly get some wierd tracebacks.

Buggered if I know where though -- "you are in a maze of
twisty function calls, all alike" :-/

Some playing with a debug build and gdb coming up...

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=676155&group_id=5470