Martin wrote: > [email protected] píše v Út 02. 08. 2011 v 13:30 +0200: > > There are probably two reasons: > > 1. the plugin loader searchs in the filesystem and load found files > > 2. Often used possibility to add own plugins > > > > I'm aware that's not an optimal setup... > > 1) Would it mind if you have plugins twice available with your > executable? > Once bundled and once directly added to he directory with your > executable? > - with this way you would have dependencies there and still have them > available in the filesystem. Or do you care a lot about space?
I filter the result from Analyses(). Thereby PyInstaller collects only the dependencies and not the plugin code. > 2) Another approach would be change the plugin loader at runtime to > return a fixed list of plugins. Something similar is implemented in > django import hook for commands module from django. It's a user requirement to use custom plugins additional to the bundled plugins. It looks like there is no way to grab dependencies only. Isn't it? Carsten -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyinstaller?hl=en.
