[Pythonmac-SIG] Problems installing Python 1.5.1 for Mac
Just van Rossum
Tue, 19 May 1998 11:46:21 +0200
At 12:36 PM +1000 5/19/98, Adam Weisser wrote:
>I'm having problems trying to install Python 1.5.1 for Mac on a 8500/180
This particular configuration should be no problem: a friend of mine uses
an 8500 running 7.5.5, and Python is quite happy there.
>After installation, when it tries to run the configure
>script, it comes up immediately with the following error:
>'import exceptions' failed; use -v for traceback
>defaulting to old style exceptions
>'import site' failed; use -v for traceback
>Traceback (innermost last):
> File "flap:jack:Python:Mac:scripts:ConfigurePython.py", line 11, in ?
>ImportError: No module named os
Hmm, that's bad. Apparently there's something wrong with sys.path,
since it can't find the first non-builtin module ConfigurePython tries to
import. What install options did you choose?
Please remove the Python 1.5.1 prefs file from the prefs folder
and run ConfigurePython again. If it still doesn't work, please
start the interpreter and do something like this:
Python 1.5.1 (#37, Apr 27 1998, 13:36:04) [CW PPC w/GUSI w/MSL]
Copyright 1991-1995 Stichting Mathematisch Centrum, Amsterdam
>>> import sys
['', ':', 'DevDev:PyPy:Python 1.5.1:', 'DevDev:PyPy:Python 1.5.1:Lib',
'DevDev:PyPy:Python 1.5.1:PlugIns', 'DevDev:PyPy:Python 1.5.1:Lib:lib-tk',
'DevDev:PyPy:Python 1.5.1:Mac:Lib', 'DevDev:PyPy:Python
1.5.1:Mac:Lib:lib-scripting', 'DevDev:PyPy:Python 1.5.1::LibLetterror',
'DevDev:PyPy:Python 1.5.1:Extensions:NumPy', 'DevDev:PyPy:Python
Do the pathnames printed exist? (Especially the :Lib, :Mac:Lib and :PlugIns
Is there enough disk space? (Just guessing, the installer should complain
about that, but I'm not sure how Python applets/scripts react.)
>We also had similar problems installing on a 8100/100 running 7.6.2.
>Both machines have 200+ Mb RAM and have virtual memory switched off.
Should be no problem.
>I also tried decreasing memory allocations to no avail.
>This problem requires an urgent solution, so please get back to me so I
>don't have to rewrite the thing in C!!!!!!
Which I'm sure will take longer than fixing the Python setup...
Good luck, and let us know what happens!
(And if others have experienced similar problems: please let us know.)