On sab, 2010-11-06 at 20:20 +0800, est wrote: > Hi Python hackers, > > Is there anything remaining in python26.dll could be ripped before > shipment? The debugger, interactive console, .py parser(only the .pyc > is useful), etc is useless for a final shipping product made by > pyinstaller. > > Just an idea, hope someone could try it out :D
I've long been thinking of maintaining a Python "fork" (or patch if you prefer) to reduce its footprint by modularization. For instance, about 40% of python26.dll is made of CJK tables for East-Asian language codecs. While there are some applications that surely need it, I think it's fair to assume that most don't. When PyInstaller will grow an option to specify which codecs are really needed, it would be really helpful if those tables were available *externally*, so that would not be bundled on applications that don't require them. As a further point, PyQt applications currently ship those tables twice, because they are also part of Qt's own codec system. -- Giovanni Bajo :: Develer S.r.l. [email protected] :: http://www.develer.com Blog: http://giovanni.bajo.it Last post: Compile-time Function Execution in D -- 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.
