Hi, First off, thanks to the authors for this great utility. I have an application which is entirely compiled to pyd files using cython except for the initial startup script which is a normal .py file. Because of this I have a bunch of hidden imports as expected. The trouble I am having is that a number of the hidden imports are packages as opposed to individual modules. When I list a package in hidden_imports, it seems that the dependency analysis that is done when pyinstaller sees the import in the actual .py file is not done when I list the package in hidden_imports.
As an example, I use psutils. If I simply list 'psutils' in hidden imports, the application fails due to missing modules. I need to add 'psutil._common', 'psutil._compat', 'psutil._pswindows' in hidden imports and then add _psutil_windows.pyd and socket.pyd to the binaries set to successfully run the app. I have similar issues with wx Python Phoenix and even ctypes, which I am having a hard time overcoming by adding dependencies in the spec file. I am however, able to fix this if I explicitly import them in the initial .py file, even though I am not using them in that part of the application. I would prefer not to import them in the initial script due to 'security' reasons - the first thing my initial pyd file does is some hash integrity checks on the package to ensure that nothing has been altered or injected, including pyinstaller's own metapath hooks. Is there a way to ask pyinstaller to look for dependencies of a package listed in hidden_imports? Thanks for any help or insight you can share. -- 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.
