Python import mechanics

by

The first thing you should know is that the Python language is NOT an ISO standard. This is rather different from C/C++, and it means that there’s no “proper” way to define a language behaviour – CPython might do something just because it was coded that way, and Jython might do the other way round.

about your questions, remember that “importing” a module is a two-part operation: first the module is loaded – if it had never been, e.g. if it wasn’t available in sys.modules, then a name is bound to that module in the local namespace.

hence:

1) Yes, you can reference whatever you want from module a by providing the proper namespace, e.g. you’ll have to do something like

B.C.name = “something”

And I think this is very rarely done in Python programs and could be considered bad practice since it forces a “transitive dep” – if some module B implementation is refactored and doesn’t depend on C anymore, it should continue offering the C module just for satisfying A deps.

Of course setting __ all __ can prevent this, and a good practice may be to put __ all __ in all your modules, and export just the symbols you want to be really public.

2) Yes and no. Doing 

import a.b.c.d

performs the first import phase (loading) on all modules, but the second just on a (and, recursively, in b with respect to c, etc) but all the modules in the chain must be referenced by full namespace; after such an import, you can do

a.something
a.b.something
a.b.c.something

but you can’t do 

c.something
b.something

I must admit that kind of usage is pretty rare as well; I generally prefer the “from module import something” way-to-import, and generally you just ask for what you need – such nesting is neither common in libraries, nor its usage is that common.

Many times there’re “outer packages”, just used for organization, which hold modules with classes. It’s very likely that a, b, c above are just packages, and d is a module which truly holds classes, functions and other objects. So the proper usage would be:

from a.b.c.d import name1, name2, name3

I hope this satifies your curiosity.

More Related Contents:

  1. `from … import` vs `import .` [duplicate]
  2. Adding a module (Specifically pymorph) to Spyder (Python IDE)
  3. Import module from subfolder
  4. Python: importing a sub‑package or sub‑module
  5. Can’t import my own modules in Python
  6. Can’t import my own modules in Python
  7. How to import module when module name has a ‘-‘ dash or hyphen in it?
  8. How to import all submodules?
  9. Modules are installed using pip on OSX but not found when importing
  10. Python module with a dash, or hyphen (-) in its name
  11. How to change a module variable from another module?
  12. Use a library locally instead of installing it
  13. How does Python importing exactly work?
  14. How to access a standard-library module in Python when there is a local module with the same name?
  15. How to import a Python module from a sibling folder?
  16. How to import a module in Python with importlib.import_module
  17. What could cause a python module to be imported twice?
  18. Namespaces with Module Imports
  19. How to prevent a module from being imported twice?
  20. ImportError on python 3, worked fine on python 2.7
  21. Python importing a module from a parallel directory
  22. How to make global imports from a function?
  23. how to test if one python module has been imported?
  24. from … import OR import … as for modules
  25. Relative import in Python 3 is not working [duplicate]
  26. Flask(‘application’) versus Flask(__name__)
  27. python import module from parent package
  28. How to reference python package when filename contains a period
  29. Forced naming of parameters in Python
  30. Trace Python imports

Leave a Comment