tags:

views:

80

answers:

4

Hi,

If I have a file myfile.py, which imports Class1 from file.py and file.py contains imports to different classes in file2.py, file3.py, file4.py.

In my myfile.py, can I access these classes or do I need to again import file2.py, file3.py etc...

My question is whether python automatically add all the imports included in the file I imported, and can I use them automatically.

Thank you. Bala

+1  A: 

Python doesn't automatically introduce anything into the namespace of myfile.py, but you can access everything that is in the namespaces of all the other modules.

That is to say, if in file1.py you did from file2 import SomeClass and in myfile.py you did import file1, then you can access it within myfile as file1.SomeClass. If in file1.py you did import file2 and in myfile.py you did import file1, then you can access the class from within myfile as file1.file2.SomeClass. (These aren't generally the best ways to do it, especially not the second example.)

This is easily tested.

Mike Graham
But please, please, please don't do this. Explicitly import all modules your code will need.
Ignacio Vazquez-Abrams
Yes and no. Depending on how file1.py is supposed to work, it might be the right place from which to access `SomeClass`. (The latter example is always bad form.)
Mike Graham
A: 

In the myfile module, you can either do from file import ClassFromFile2 or from file2 import ClassFromFile2 to access ClassFromFile2, assuming that the class is also imported in file.

This technique is often used to simplify the API a bit. For example, a db.py module might import various things from the modules mysqldb, sqlalchemy and some other helpers. Than, everything can be accessed via the db module.

tux21b
A: 

if you are using wild import, yes, wild import actually is the way of creating new aliases in your current namespace for contents of the imported module. if not, you need to use the namespace of the module you have imported as usual.

M. Utku ALTINKAYA
Of course, you should never ever ever use `import *`.
Mike Graham
+2  A: 

Best practice is to import every module that defines identifiers you need, and use those identifiers as qualified by the module's name; I recommend using from only when what you're importing is a module from within a package. The question has often been discussed on SO.

Importing a module, say moda, from many modules (say modb, modc, modd, ...) that need one or more of the identifiers moda defines, does not slow you down: moda's bytecode is loaded (and possibly build from its sources, if needed) only once, the first time moda is imported anywhere, then all other imports of the module use a fast path involving a cache (a dict mapping module names to module objects that is accessible as sys.modules in case of need... if you first import sys, of course!-).

Alex Martelli