On Tue, Nov 15, 2011 at 12:16 AM, Hartmut Goebel <[email protected] > wrote:
> > Have you read the section about Hooks (http://www.pyinstaller.org/** > export/latest/trunk/doc/**Manual.html#hooks<http://www.pyinstaller.org/export/latest/trunk/doc/Manual.html#hooks> > ). > > I must admit, that the Manual is not quite clear about this. I will try to > improve the text. > That would be good, but I think what is more important is that to me, it is not clear what pyinstaller is trying to do. It is trying to assemble a run-time environment that contains everything the app needs, yes, but what are all those pieces? And how are they arranged and connected to each other? You need to explain that first. I am a programmer who just writes python code, grabs modules from pypi as needed, tries it out, great, it works! now let's magically make a package! -- it is not at all obvious where all the pieces live and what ties them together in the NORMAL situation, much less in a bundled app. You are immersed in it but you have left it all unstated and implied in the doc. (Which means I am sure, you are not getting enough credit for your cleverness!) After you explain the structure of the end goal (the app bundle) you say, so here is how pyinstaller finds out all it needs to know to reach this situation in the normal case. But the big difficulty comes with apps that do such-and-so, and the way around this is... -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
