On Sunday 06 August 2006 6:30 pm, Giovanni Bajo wrote: > Jeremy Kloth wrote: > >> The main difference is that PyInstaller has a flexible hook-based > >> system which allows to bundle those hooks *within* PyInstaller > >> itself. I suggest you give a look to the "hooks" directory in the > >> PyInstaller distribution. > > > > The same option is available to users of py2exe. It just that 4Suite > > incorporates the hook for the user so a new release of 4Suite works > > with py2exe automatically, without waiting for another release of > > py2exe for it to work correctly. It is the same thing either way. > > Are you speaking of that hackerish of "use my own distutils-derived > classes", that its Ft.Lib.DistExt.Py2Exe? I don't consider that a real > solution to the problem, comparable to PyInstaller's hook system.
There is nothing directly distutils with that. It is completely py2exe, which happens to use distutils as its engine. > There are at least two big issues. First, the user has *still* to be aware > of the existence of the hook and explicitally call it in its setup.py file. > Second, this kind of "hooks" cannot be chained together: what if my > application uses 3 or 4 third party modules, each one with its own > distutils derived classes? Sure there is a one-liner that needs to be used instead of the standard py2exe one, but it is better telling users "sorry our brand new shiny release cannot be frozen until PyInstaller cuts a new release that supports our changes". If you can tell me how a brand new 4Suite release can work OOTB witth any PyInstaller version, I'd be glad to hear it. 4Suite is a large complicated beast of a library so it tends to stress tools to their limits. It is just the py2exe is easily extended to support our needs without needing cooperation from the py2exe maintainers. Releasing 4Suite is enough work without being tied to yet another release schedule. -- Jeremy Kloth http://4suite.org/ _______________________________________________ PyInstaller mailing list [email protected] http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
