[ python-Bugs-970799 ] Pyton 2.3.4 Make Test Fails on Mac OS X

SourceForge.net noreply at sourceforge.net
Mon Jun 28 18:16:58 EDT 2004


Bugs item #970799, was opened at 2004-06-10 16:42
Message generated for change (Comment added) made by dekiefer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=970799&group_id=5470

Category: Build
Group: Python 2.3
Status: Open
Resolution: None
Priority: 3
Submitted By: D.  Evan Kiefer (dekiefer)
Assigned to: Brett Cannon (bcannon)
Summary: Pyton 2.3.4 Make Test Fails on Mac OS X

Initial Comment:
Under Mac OSX 10.3.4 with latest security update.
Power Mac G4 733MHz

Trying to install Zope 2.7.0 with Python 2.3.4.

I first used fink to install 2.3.4 but Zope could find module 'os' to 
import. 

I then followed the instructions at:
http://zope.org/Members/jens/docs/Document.2003-12-27.2431/
document_view to install Python with the default configure.

Unlike under fink, doing this allowed me to run 'make test'. It too 
noted import problems for 'os' and 'site'.

test_tempfile
'import site' failed; use -v for traceback
Traceback (most recent call last):
  File "/Volumes/Spielen/Python-2.3.4/Lib/test/tf_inherit_check.py", 
line 6, in ?
    import os
ImportError: No module named os
test test_tempfile failed -- Traceback (most recent call last):
  File "/Volumes/Spielen/Python-2.3.4/Lib/test/test_tempfile.py", 
line 307, in test_noinherit
    self.failIf(retval > 0, "child process reports failure")
  File "/Volumes/Spielen/Python-2.3.4/Lib/unittest.py", line 274, in 
failIf
    if expr: raise self.failureException, msg
AssertionError: child process reports failure


test_atexit
'import site' failed; use -v for traceback
Traceback (most recent call last):
  File "@test.py", line 1, in ?
    import atexit
ImportError: No module named atexit
test test_atexit failed -- '' == "handler2 (7,) {'kw': 'abc'}\nhandler2 
() {}\nhandler1\n"
test_audioop

----------
test_poll skipped -- select.poll not defined -- skipping test_poll
test_popen
'import site' failed; use -v for traceback
'import site' failed; use -v for traceback
'import site' failed; use -v for traceback
test_popen2


-------------------
229 tests OK.
2 tests failed:
    test_atexit test_tempfile
24 tests skipped:
    test_al test_bsddb3 test_cd test_cl test_curses test_dl
    test_email_codecs test_gl test_imgfile test_largefile
    test_linuxaudiodev test_locale test_nis test_normalization
    test_ossaudiodev test_pep277 test_poll test_socket_ssl
    test_socketserver test_sunaudiodev test_timeout test_urllibnet
    test_winreg test_winsound
Those skips are all expected on darwin.
make: *** [test] Error 1
deksmacintosh:3-> 

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

>Comment By: D.  Evan Kiefer (dekiefer)
Date: 2004-06-28 15:16

Message:
Logged In: YES 
user_id=318754

Thanks Jack, I'll try that.

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

Comment By: Jack Jansen (jackjansen)
Date: 2004-06-28 14:12

Message:
Logged In: YES 
user_id=45365

My guess is that something in your environment is messing things up. 
Various of the tests that give the "import site failed" message use 
subprocesses.

What I tend to do to debug issues like this is create a new dummy user 
(I tend to use the short name "luser" and the long name "Bill Gates":-), 
unpack a fresh distribution under that account and try building.

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

Comment By: D.  Evan Kiefer (dekiefer)
Date: 2004-06-28 10:54

Message:
Logged In: YES 
user_id=318754

Do you get these failures if you compile Python from scratch
instead of using Fink?  How about running the tests directly?

See above, the second time I installed without fink and ran the tests 
directly. The errors are from 'make test' done without fink.

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

Comment By: Brett Cannon (bcannon)
Date: 2004-06-17 14:31

Message:
Logged In: YES 
user_id=357491

Do you get these failures if you compile Python from scratch instead of 
using Fink?  How about running the tests directly?

I suspect the test_atexit failure is a Fink-specific issue and the 
test_tempfile failure was just a timing quirk since it has a threaded and 
that can make it sensitive to timing.

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

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



More information about the Python-bugs-list mailing list