[Python-bugs-list] [ python-Bugs-422339 ] 1 test failed: test_format

[noreply@sourceforge.net]

Bugs item #422339, was updated on 2001-05-08 08:23
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=105470&aid=422339&group_id=5470

Category: Python Interpreter Core
Group: Platform-specific
Status: Closed
Resolution: Wont Fix
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: 1 test failed: test_format 

Initial Comment:
Hallo!

OS:

OSF1 alpha04.faidor.de V4.0 1530 alpha

# cc -V
cc  (cc)
        Digital UNIX Compiler Driver 3.11
Compaq C V6.1-120 on Digital UNIX V4.0G (Rev. 1530)


Compiling and testing:

**********************************************************************
test_format
**********************************************************************
Then ...
We expected (repr): ''
But instead we got: "'%#o' % 0 == '00' != '0'"
test test_format failed -- Writing: "'%#o' % 0 == 
'00' != '0'", expected: ''


Version Python-2.1

Remark:

I found this error three times in the year 2000,
but resolved and for other Platforms

Kind regards
Hermann


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

Comment By: Nobody/Anonymous (nobody)
Date: 2001-05-09 01:30

Message:
Logged In: NO 

Hello!

Now I tried with gcc 
and the same error appears. Why?

./configure --prefix=/opt_prog/local --with-gcc
gmake 
gmake test
-------
Then ...
We expected (repr): ''
But instead we got: "'%#o' % 0 == '00' != '0'"
test test_format failed -- Writing: "'%#o' % 0 == '00' != 
'0'", expected: ''
--------


and the whole thing is compiled with gcc.(2.95.3)

Hermann


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

Comment By: Tim Peters (tim_one)
Date: 2001-05-09 01:29

Message:
Logged In: YES 
user_id=31435

Sorry, I see nothing surprising about Python using whatever 
cc resolves to by default on the system.  If you don't want 
C programs to use cc, change cc.

If you want it to use gcc on this platform instead, you 
should open a different bug report, or, better, supply a 
patch to the Unix config process:  the chance that any 
active Python developer uses this particular plaform is 
approximately 0, so that's also the chance that anyone can 
write and test a config change for you.


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

Comment By: Nobody/Anonymous (nobody)
Date: 2001-05-09 01:10

Message:
Logged In: NO 

Hermann.Rochholz@gmx.de

Hello!

But why doesn't python use the gcc?
It's installed and every program I've translated before 
uses it automatiocally.

Regards
Hermann



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

Comment By: Tim Peters (tim_one)
Date: 2001-05-08 18:12

Message:
Logged In: YES 
user_id=31435

The Compaq compiler is in violation of the C std if it 
produces "00" for printf("%#o", 0), and all Python does 
here under the covers is call the platform sprintf.

Sometimes we put ugly stuff inside Python to worm around 
platform C bugs, but in this case the Compaq compiler is 
the only known offender.  Not worth it.  If

printf("%#o", 0)

does produce two zeroes in a C program using this compiler, 
file a bug with them.  Does it?  I'm closing this as "won't 
fix" assuming it does.


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

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