Jared said, There is a main.py that is the top level executable, but it needs to be able to launch all of the other scripts as separate processes.
Marin said, > > Please look at the latest improved doc. It contains more information: > > > http://htmlpreview.github.com/?https://github.com/pyinstaller/pyinstaller/blob/develop/doc/Manual.html > > There are also examples in the distribution folder. However, it is not clear to me if your app is really a "multipackage" one in the sense of the doc. The point of the "multipackage" feature is to minimize the disk usage of separate, individual apps that use a common code base. So they can share a single copy of bulky DLLs or data files. Your description of a main that starts the others as processes sounds like a single app. Can you be more specific about the structure of this system? What is the process creation mechanism? Does main.py import sub1.py, etc. with import statements? Or does it do some kind of dynamic import at runtime? Or does it use OS facilities to launch them as separate programs? Also, one-file or one-dir bundling? -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
