Archive files solves the problem for Python modules. But that leaves the problem of dynamically loaded modules. And resources for dialogs and such, if you use native GUI stuff on Mac or Windows. And most serious applications that I've seen (GRiNS and Zope, to name two, Mailman is the only exception I can think of) depend on non-standard plugin modules. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
Jack Jansen wrote:
Point taken. For dynamically loaded modules, I believe in following the native system's DLL path, and not adding eccentric Python logic. But many disagreed a couple week's ago when I raised this. For resources, I think the archive file can accommodate this, although it seems highly system dependent. Anyway, any file at all can live in the archive and the import mechanism for *.pyc will not be damaged nor unduly slowed down by its presence. JimA
Jack Jansen wrote:
Point taken. For dynamically loaded modules, I believe in following the native system's DLL path, and not adding eccentric Python logic. But many disagreed a couple week's ago when I raised this. For resources, I think the archive file can accommodate this, although it seems highly system dependent. Anyway, any file at all can live in the archive and the import mechanism for *.pyc will not be damaged nor unduly slowed down by its presence. JimA
participants (2)
-
Jack Jansen -
James C. Ahlstrom