Am -10.01.-28163 20:59, schrieb Hartmut Goebel: > *So I can only imagine, either the current dir is different or > sys.path is different.* Okay, I think, I found the reason: <http://bytes.com/topic/python/answers/608227-2-4-2-5-current-directory-change> Explains it well.
This works fine here, since I have the current dir on PYTHONPATH and by
tests were wrong:
PYTHONPATH= python -sS utils/Build.py
works, but this put "" (the current dir) on sys.path
$ PYTHONPATH=/tmp python -sS utils/Build.py
Traceback (most recent call last):
File "utils/Build.py", line 22, in <module>
import PyInstaller.build
ImportError: No module named PyInstaller.build
Now this fails as you experienced.
So first of all I'm change all my startup scripts to not pout an empty
component into PYTHONPATH
Then we'll think about a solution :-)
--
Schönen Gruß - Regards
Hartmut Goebel
Dipl.-Informatiker (univ.), CISSP, CSSLP
Goebel Consult
Spezialist für IT-Sicherheit in komplexen Umgebungen
http://www.goebel-consult.de
Monatliche Kolumne: http://www.cissp-gefluester.de/
Goebel Consult mit Mitglied bei http://www.7-it.de
smime.p7s
Description: S/MIME Cryptographic Signature
