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 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? -- Giovanni Bajo _______________________________________________ PyInstaller mailing list [email protected] http://lists.hpcf.upr.edu/mailman/listinfo/pyinstaller
