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:

Are these the *actual* names of your files and directories?  Please repost using actual real real names and paths, if not.

If these *are* the actual names of the files and directories, the problem is that you are using an out-of-date version of setuptools that doesn't put "-script" in the filenames of scripts to be run using an .exe.

That, and there is probably also something terribly wrong with your setup.py.

However, if the above are *not* the real names of the files and directories involved, please repost and provide them, because it might be something else altogether.



_______________________________________________
Distutils-SIG maillist  -  [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig

Reply via email to