I'm working on the "About Hooks" manual section. In large part it is documentation of the things a hook can import from compat or from utils.hooks.
As of now I am leaning toward NOT documenting the following items: compat.exec_command* (three methods in all). It seems to me that the utils.hooks.exec_* and utils_hooks.eval_* methods are sufficient. Does anyone know of a use case where a hook would require compat.exec_command() and could not use utils.hooks.exec_statement() instead? utils.hooks.exec_script() and eval_script(). The only use case I can think of is if you are creating a family of related hooks and you could factor out some very complex calculation to a script in utils/hooks/subproc. Which seems unlikely to me. Or does these have some use in the special pre-safe* or pre-find* hooks? opengl_arrays_modules() As noted in the code, this is only used in one hook and will be moved to that hook. All the Qt4 and Qt5 special functions such as qt5_qml_dir(). These are only used from the PyQt (and PySide) hooks which already exist. -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller. For more options, visit https://groups.google.com/d/optout.
