Hi Thomas Heller,
Thanks for such a quick reply. I should comment it while it's still
hot.
I have a problem with this new release of py2exe, 0.5.0. I
came to this when I built an executable for my "psi baby",
Pages Persos Chez.com
psi is Python shell (à la PyShell) where the user can import
modules on the fly, likeimport mymodule
I had not this problem with the previous py2exe releases.
...
This is by intent. The py2exe'd exe-file runs with the minimal sys.path
possible, and that is the one where only the 'library.zip' archive is
in.
Ok, I'm glad I understood the problem correctly.I should
say I'm "half-satisfied" with this. I think including *at least* the home
dir of the application in the sys.path will not increase the sys.path
too much.
Let's take a practical example. I create an application that uses
py modules, which should be loaded on the fly. I can put
them in a separate dir or in the home dir, they will be packed
- and they are - in the library.zip during the creation of the exe.
That's fine.
Now take an exe, where the extension modules are created
after the exe has been built For example, modules created by
the users, that extend the application. How can I have a direct
and a simple access to them? Having these extension molules
in the application path seems to be natural.
May I humbly suggest, you make some tests with my psi
application?
So I'm asking, is it possible to force the home dir to be
in the sys.path?
(I have some ideas)
Just writing this mail, this comes to my mind, however not
tested. An application calling an help file with an
os.startfile('blablalba.htm')
Regards
Jean-Michel Fauth, Switzerland