dynamic import

[bry]

Hi,
I'm trying to do a dynamic import of a file that has no problems with it, that
is to say I can import it normally, my sys.path is set to the right folder etc.
but my dynamic import code is not working, this is the problem code:

try:
import f[0]
except:
print "not importable"

f[0] returns the name of the file I'm importing, so I suppose this is a typing
problem, should I change f[0] to be some other type?

I've also tried
t = "import " + f[0]
try:
eval(t)
except:
print "not importable"

but I always get "not importable"

[Nick Smallbone]

<br*@itnisk.com> wrote in message
news:ma*************************************@pytho n.org...

Hi,
I'm trying to do a dynamic import of a file that has no problems with it, that is to say I can import it normally, my sys.path is set to the right folder etc. but my dynamic import code is not working, this is the problem code:

try:
import f[0]
except:
print "not importable"

f[0] returns the name of the file I'm importing, so I suppose this is a typing problem, should I change f[0] to be some other type?

I've also tried
t = "import " + f[0]
try:
eval(t)
except:
print "not importable"

but I always get "not importable"

That's because eval evaluates an expression and returns the result. To
execute a statement you need to use exec(t) instead.

Nick

[Duncan Booth]

br*@itnisk.com wrote in
news:ma*************************************@pytho n.org:

Hi,
I'm trying to do a dynamic import of a file that has no problems with
it, that is to say I can import it normally, my sys.path is set to the
right folder etc. but my dynamic import code is not working, this is
the problem code:

try:
import f[0]
except:
print "not importable"

f[0] returns the name of the file I'm importing, so I suppose this is
a typing problem, should I change f[0] to be some other type?

No. The import statement takes the name of a module, it doesn't take a
string. For example, instead of:

import sys
print sys.version

you are trying to do the equivalent of:

import "sys"
print "sys".version

You wouldn't expect the second line to work, so why should you expect the
first line to work? If it did work, how would you expect to refer to the
module it imported?

In this case your solution is to use the __import__ builtin. My example
becomes:

module = __import__("sys")
print module.version

[Peter Otten]

br*@itnisk.com wrote:

I'm trying to do a dynamic import of a file that has no problems with it,
that is to say I can import it normally, my sys.path is set to the right
folder etc. but my dynamic import code is not working, this is the problem
code:

try:
import f[0]
except:
print "not importable"

f[0] returns the name of the file I'm importing, so I suppose this is a
typing problem, should I change f[0] to be some other type?

I've also tried
t = "import " + f[0]
try:
eval(t)
except:
print "not importable"

but I always get "not importable"

Let's see.

import f[0] File "<stdin>", line 1
import f[0]
^
SyntaxError: invalid syntax

So python won't accept the [0] stuff here.
f = "os"
import f Traceback (most recent call last):
File "<stdin>", line 1, in ?
ImportError: No module named f

So python doesnt try to resolve f as a variable name but rather as a
literal.
eval("import os") Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "<string>", line 1
import os
^
SyntaxError: invalid syntax exec "import os"
So the eval() function chokes if you feed it an import statement (actually
any statement).

Quoted from http://docs.python.org/lib/built-in-funcs.html#l2h-23

"""Hints: dynamic execution of statements is supported by the exec
statement."""

Putting it together:
f = ["os"]
exec "import " + f[0]
os

<module 'os' from '/usr/local/lib/python2.3/os.pyc'>

Heureka :-)

Now, did you see how useful Python's tracebacks are and how much information
you lose by a bare try ... except?

try:
...
except ImportError:
...

would have been fine, by the way.

Peter

[John Roth]

<br*@itnisk.com> wrote in message
news:ma*************************************@pytho n.org...

Hi,
I'm trying to do a dynamic import of a file that has no problems with it, that is to say I can import it normally, my sys.path is set to the right folder etc. but my dynamic import code is not working, this is the problem code:

try:
import f[0]
except:
print "not importable"

the import statement unfortunately doesn't take a string at
run time. As Duncan says, you need to use the
__import__() builtin. Read up on it in the library
reference (it's the very first entry in the builtins section,)
because there are some considerations in using it that
aren't exactly obvious on first glance.

The other alternative is something like:

exec "import " + f[0]

This will work as well, and it might be a bit clearer, depending
on what you're trying to do.

John Roth

[510046470588-0001]

"John Roth" <ne********@jhrothjr.com> writes:

the import statement unfortunately doesn't take a string at
run time. As Duncan says, you need to use the
__import__() builtin. Read up on it in the library
reference (it's the very first entry in the builtins section,)
because there are some considerations in using it that
aren't exactly obvious on first glance.

The other alternative is something like:

exec "import " + f[0]

This will work as well, and it might be a bit clearer, depending
on what you're trying to do.

if one calls the __import__ function with the same argument several times,
will the module be cached inbetween?

Klaus Schilling

[John Roth]

<51***************@t-online.de> wrote in message
news:87************@debian.i-did-not-set--mail-host-address--so-shoot-me...

"John Roth" <ne********@jhrothjr.com> writes:

the import statement unfortunately doesn't take a string at
run time. As Duncan says, you need to use the
__import__() builtin. Read up on it in the library
reference (it's the very first entry in the builtins section,)
because there are some considerations in using it that
aren't exactly obvious on first glance.

The other alternative is something like:

exec "import " + f[0]

This will work as well, and it might be a bit clearer, depending
on what you're trying to do.
if one calls the __import__ function with the same argument several times,
will the module be cached inbetween?

You should get the same copy of the module.

John Roth
Klaus Schilling