On 3/3/2008 1:07 PM, [EMAIL PROTECTED] wrote: > I've studied pkg_resources a bit in the meantime, and it seems to me > that supporting PyOpenGL 3 requires support for eggs. This because > PyOpenGL uses egg entry points to find parts of its implementation > (pluggable components).
I don't know what an "egg entry point" is... > Are major changes to PyInstaller's packaging > model necessary to be able to include eggs? Depends on what you mean by "egg". Currently, if you have a package installed as an .egg directory, PyInstaller correctly packages it since it's simply a directory in the PYTHONPATH, but the .py/.pyd/.so files are extracted one by one and included into the generated executable; .egg metadatas are *not* packaged in any way. ".egg" files are not supported (just like .zip files that are in PYTHONPATH, that is the "zip import" core feature). If you have a package installed as a .egg file, PyInstaller will not be able to look inside it and extract the required files. If I understand you correctly, this "egg entry point" feature probably relies on the .egg metadata information which is lost when packaging with PyInstaller. -- Giovanni Bajo Develer S.r.l. http://www.develer.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
