|
Thanks for your response. Yes, these are not the real names. My situation is (using real names, but using only relevant files): /bots/ engine.py transform.py botslib.py __init__.py /usersys/ __init__.py /mappings/ __init__.py 02ordersedi2aperak.py so: engine.py is the start point. engine.py imports botslib.py (initialises global), imports transform.py and starts function from transform.py transform imports botslib.py, imports usersys.mappings.02ordersedi2aperak.py usersys.mappings.02ordersedi2aperak.py imports botslib.py->in this import it is initialised again. for an email I send later (but I messed up so that its not in the same thread): I examined which modules python has imported (sys.modules). when using the .exe in Scripts dir, most imports have 'bots' inserted before the module name, eg: 'bots.botlib' but when importing from 02ordersedi2aperak.py, this does not happen; it is imported as 'botslib' So that is why python thinks it is another module. This does not happen when running start.py directly (as 'python engine.py') best regards, Henk-Jan Phillip J. Eby wrote:
|
_______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
