Matteo Baracani píše v Po 23. 04. 2012 v 14:40 +0200: > In bootloader the idea is to change the loadPython function, so that > before throwing an error when not finding the bundled libpython, the > function checks the presence of a system libpython (how this search > is > performed in detail depends on the operating system). In my planned > implementation the system libpython's version must match the same > that > could be found on the build machine. If nothing is found the program > throws an error.
I have another proposal. Your plan looks like it's time to implement metadata support in bootloader: http://www.pyinstaller.org/ticket/371 With this feature implemented it could work this way: - bootloader reads libpython file name from its metadata - bootloader reads from metadata whether to use bundled or system libpython. - bootloader looks for libpython in defined place - the program throws an error if libpython is not found in defined place > > If somebody wants to comment on the above, I'll gladly take your > suggestions into account during development. > > Matteo Is this feature anything you really need or you have to have? What is your real scenario? Is it only a feeling you could save a few MB by excluding libpython? I think this feature will introduce other issues: - how to handle dynamically loadable native python modules from standard library? - at least pyinstaller on mac will be broken because it expects libpython to be available in the same directory as other dynamic libraries. It is not as straightforward as you would think. What platform is your main focus? However, do not expect this feature to be included in 2.0. Probably later releases. -- 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.
