[ python-Bugs-1370322 ] Float marshaling problems with test_colorsys

SourceForge.net noreply at sourceforge.net
Sat Dec 10 12:47:13 CET 2005


Bugs item #1370322, was opened at 2005-11-30 19:49
Message generated for change (Comment added) made by mwh
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1370322&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Interpreter Core
Group: Python 2.5
Status: Open
Resolution: None
Priority: 7
Submitted By: Reinhold Birkenfeld (birkenfeld)
Assigned to: Michael Hudson (mwh)
Summary: Float marshaling problems with test_colorsys

Initial Comment:
Starting point: "make clean; make" in the 2.5 source tree.

"make test" hangs at test_colorsys.

Careful investigation shows that when the bytecode is
freshly generated
by "make all" (precisely in test___all__) the .pyc file
is different from what a
direct call to "regrtest.py test_colorsys" produces.

Curiously, a call to "regrtest.py test___all__" instead
of "make test" produces
the correct bytecode.

System is Linux 2.6, x86, gcc 3.4.4.

I have attached both versions of colorsys.pyc.

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

>Comment By: Michael Hudson (mwh)
Date: 2005-12-10 11:47

Message:
Logged In: YES 
user_id=6656

Also, is the problem reproducable on *your* system?  AFAIK, noone else has 
reproduced it, but I don't know how many people are actually running make test 
on development Python these days...

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

Comment By: Michael Hudson (mwh)
Date: 2005-12-10 11:43

Message:
Logged In: YES 
user_id=6656

I don't think so, no.  For a start, I can't reproduce the problem (mind you, I only 
use a Mac regularly these days).

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

Comment By: Reinhold Birkenfeld (birkenfeld)
Date: 2005-12-10 11:07

Message:
Logged In: YES 
user_id=1188172

Michael, you lately corrected a problem with floatobject.
Although the problem persists here, could it be caused by a
similar bug?

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

Comment By: Armin Rigo (arigo)
Date: 2005-12-01 10:32

Message:
Logged In: YES 
user_id=4771

It's again a problem with floats.  For example, the constant 0.3 in rgb_to_yiq shows up as 0.0 in bad.pyc.  The constant 1.72986 shows up as 1.0.

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

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


More information about the Python-bugs-list mailing list