Sure no problem with import, if the module to import is fixed. I suggested __import__ because he was speaking of plugin-like behaviour, in which case it is common to not know the name of the module until run time. On 3 Jun 2013 17:06, "Hartmut Goebel" <[email protected]> wrote:
> Am 03.06.2013 22:13, schrieb Daniel Hyams: > > > This should be no problem; just use __import__ as usual. > > > Hmm, well *I* usually doe not use `__import__()`, but `import`. Why it > should be required to use __import__? > > > -- > Schönen Gruß > Hartmut Goebel > Dipl.-Informatiker (univ), CISSP, CSSLP > > Goebel Consult > http://www.goebel-consult.de > > Monatliche Kolumne: > http://www.cissp-gefluester.de/2012-12-in-die-cloud-in-die-cloud-ab-wo-soll-die-sein > Blog: http://www.goebel-consult.de/blog/200505010 > > Goebel Consult ist Mitglied bei http://www.7-it.de/ > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
