33 lines
1.1 KiB
Plaintext
33 lines
1.1 KiB
Plaintext
From: aa8vb at vislab.epa.gov (Randall Hopper)
|
|
Date: Mon, 19 Apr 1999 14:24:06 GMT
|
|
Subject: 'import exceptions' failed
|
|
In-Reply-To: <371B1201.392B@iname.com>; from Jussi Jumppanen on Mon, Apr 19, 1999 at 10:22:41PM +1100
|
|
References: <371B1201.392B@iname.com>
|
|
Message-ID: <19990419102406.B62714@vislab.epa.gov>
|
|
X-UID: 1682
|
|
|
|
Jussi Jumppanen:
|
|
|I have compiled the python source into a Windows DLL and using
|
|
...
|
|
|the macro runs fine and produces the expected ouput in the
|
|
|text editor, but I also get the following messages sent to
|
|
|stderr:
|
|
|
|
|
| 'import exceptions' failed; use -v for traceback
|
|
| defaulting to old style exceptions
|
|
| 'import site' failed; use -v for traceback
|
|
|
|
I don't know if your case is the same, but when I saw this, I discovered
|
|
that if $PYTHONPATH (normally used to augment Python's run-time module
|
|
search path) is defined when Python is built. This completely overrides
|
|
the default Python search path which it uses to find its own modules.
|
|
|
|
As I recall, "import exceptions" was the first thing it complained about.
|
|
I think site was the second but I'm not certain.
|
|
|
|
Randall
|
|
|
|
|
|
|
|
|