I have a library that uses: - conditional imports for windows/linux - entry_points for plugins - 3rd party libs that require hook files to work (and i dont control)
I'd like to make it easy for devs to use pyinstaller. Is there some way I can include, in my package, some entry point that allows pyinstaller to discover hidden imports? IE: I want to *package* my hooks, so devs don't have to care about them... they get automagically used if you import my lib. Again, I'd like users of my lib *not* to have to use hooks (which work fine, but i dont like them) - even though I know they are required for dependent libraries. -- 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 pyinstaller+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pyinstaller/f0847f0f-3490-485f-b17a-b314275a814e%40googlegroups.com.
