Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #91138
| Date | 2015-05-23 09:03 -0700 |
|---|---|
| Subject | Dynamic Import with sub module |
| From | Douglas Garstang <doug.garstang@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.281.1432397354.17265.python-list@python.org> (permalink) |
[Multipart message — attachments visible in raw view] - view raw
All, Can someone tell me how the following statement: import slice_fablib_common.common as common would be replicated with __import__ or import_module? I'm using fabric and I want the module when imported to appear in the namespace (which fabric shows as a task), in this case, as 'common.chef'. With the import statement it works. However, I'm trying to load the modules dynamically, and I just cannot work out what combination of options when used with dynamic imports will get me to 'common.chef'. When I get that to work, I'd like to go one step further as well. If I have modules called slice_fablib_webapp.webapp.deploy and slice_fablib_webapp.webapp.info, I'd like to import them as webapp.deploy and webapp.info. I suppose the webapp piece is a bit redundant. If I removed it, and ended up with slice_fablib_webapp.deploy and slice_fablib_webapp.info, I'd like to import them so that they still appear in fabric's name space as webapp.deploy and webapp.info. Thanks, Doug.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Dynamic Import with sub module Douglas Garstang <doug.garstang@gmail.com> - 2015-05-23 09:03 -0700
csiph-web