Python: importing a sub‑package or sub‑module

by

You seem to be misunderstanding how import searches for modules. When you use an import statement it always searches the actual module path (and/or sys.modules); it doesn’t make use of module objects in the local namespace that exist because of previous imports. When you do:

import package.subpackage.module
from package.subpackage import module
from module import attribute1

The second line looks for a package called package.subpackage and imports module from that package. This line has no effect on the third line. The third line just looks for a module called module and doesn’t find one. It doesn’t “re-use” the object called module that you got from the line above.

In other words from someModule import ... doesn’t mean “from the module called someModule that I imported earlier…” it means “from the module named someModule that you find on sys.path…”. There is no way to “incrementally” build up a module’s path by importing the packages that lead to it. You always have to refer to the entire module name when importing.

It’s not clear what you’re trying to achieve. If you only want to import the particular object attribute1, just do from package.subpackage.module import attribute1 and be done with it. You need never worry about the long package.subpackage.module once you’ve imported the name you want from it.

If you do want to have access to the module to access other names later, then you can do from package.subpackage import module and, as you’ve seen you can then do module.attribute1 and so on as much as you like.

If you want both — that is, if you want attribute1 directly accessible and you want module accessible, just do both of the above:

from package.subpackage import module
from package.subpackage.module import attribute1
attribute1 # works
module.someOtherAttribute # also works

If you don’t like typing package.subpackage even twice, you can just manually create a local reference to attribute1:

from package.subpackage import module
attribute1 = module.attribute1
attribute1 # works
module.someOtherAttribute #also works

More Related Contents:

  1. Can’t import my own modules in Python
  2. Can’t import my own modules in Python
  3. Flask(‘application’) versus Flask(__name__)
  4. python import module from parent package
  5. How to reference python package when filename contains a period
  6. beyond top level package error in relative import
  7. What is the purpose of the -m switch?
  8. `from … import` vs `import .` [duplicate]
  9. Execution of Python code with -m option or not
  10. Adding a module (Specifically pymorph) to Spyder (Python IDE)
  11. Import module from subfolder
  12. How to import members of all modules within a package?
  13. How to import module when module name has a ‘-‘ dash or hyphen in it?
  14. How to import all submodules?
  15. Modules are installed using pip on OSX but not found when importing
  16. Use a library locally instead of installing it
  17. How to access a standard-library module in Python when there is a local module with the same name?
  18. What could cause a python module to be imported twice?
  19. Namespaces with Module Imports
  20. ImportError on python 3, worked fine on python 2.7
  21. Python import mechanics
  22. Python import precedence: packages or modules?
  23. Python: import module from another directory at the same level in project hierarchy
  24. Python importing a module from a parallel directory
  25. how to test if one python module has been imported?
  26. importing a module in nested packages
  27. from … import OR import … as for modules
  28. Python modules with identical names (i.e., reusing standard module names in packages)
  29. How to properly use relative or absolute imports in Python modules?
  30. What’s the difference between a module and package in Python?

Leave a Comment