ImportError : Attempted relative import with no known parent package [duplicate]

by

It seems, from Python docs and experimenting, that relative imports (involving ., .. etc) only work if

  1. the importing module has a __name__ other than __main__, and further,
  2. the __name__ of the importing module is pkg.module_name, i.e., it has to be imported from above in the directory hierarchy (to have a parent pkg as part of it’s __name__.)

OR

the importing module is being specified via module syntax that includes a parent pkg as python -m pkg.module, in which case it’s __name__ is still __main__, so it is being run as a script, yet relative imports will work. Here __package__ is set and used to find the parent package while __name__ is __main__; more here.

[After all that, it appears that __package__ and sys.path are key to determining if/how relative imports work. __name__ indicates script or module(i.e., __main__ or module_name). __package__ indicates where in the package the relative imports occur with respect to, and the top of __package__ needs to be in sys.path.]

So, continuing with @AmitTendulkar ‘s example, if you run this as > python main.py or > python -m main or > python -m ecommerce.products from the project root directory, or enter interactive python from that root directory and import main, or import ecommerce.products the relative imports in products.py will work.

But if you > python products.py or > python -m products from within ecommerce directory, or enter interactive python from that ecommerce directory and import products they will fail.

It is helpful to add

print("In module products __package__, __name__ ==", __package__, __name__)

etc. in each file to debug.

UPDATE:

How imports work depend on sys.path and __package__, not on __name__.
Issued from /home/jj, > python sub/mod.py has a sys.path, __package__ of /home/jj/sub, None -absolute imports of modules in sys.path work, relative imports fail.

> python -m sub.mod has sys.path, __package__ of /home/jj, sub -absolute imports of modules in sys.path work, relative imports work relative to sys.path + __package__.

It is more helpful to add

import sys    
print("In module products sys.path[0], __package__ ==", sys.path[0], __package__)

etc. in each file to debug.

More Related Contents:

  1. Pylint “unresolved import” error in Visual Studio Code
  2. Should wildcard import be avoided?
  3. PyLint “Unable to import” error – how to set PYTHONPATH?
  4. Why does it say that module pygame has no init member?
  5. How do I disable a Pylint warning?
  6. Instance attribute attribute_name defined outside __init__
  7. Is it possible to ignore one single specific line with Pylint?
  8. PyLint message: logging-format-interpolation
  9. Avoid Pylint warning E1101: ‘Instance of .. has no .. member’ for class with dynamic attributes
  10. Unintentional trailing comma that creates a tuple
  11. Why is the empty dictionary a dangerous default value in Python? [duplicate]
  12. How do I get Pylint to recognize NumPy members?
  13. Pylint, PyChecker or PyFlakes? [closed]
  14. Imports failing in VScode for pylint when importing pygame
  15. pylint 1.4 reports E1101(no-member) on all C extensions
  16. Invoking Pylint programmatically
  17. How do I disable pylint unused import error messages in vs code
  18. pylint can’t find QWidget and QApplication
  19. No name ‘QApplication’ in module ‘PyQt5.QtWidgets’ error in Pylint
  20. How to run Pylint with PyCharm
  21. Running Bash commands in Python
  22. pandas select from Dataframe using startswith
  23. Putting an if-elif-else statement on one line?
  24. How to run Scrapy from within a Python script
  25. Move an item inside a list?
  26. Django: How to allow a Suspicious File Operation / copy a file
  27. clicked.connect() Error
  28. Python evaluates 0 as False
  29. Converting a csv file into a list of tuples with python
  30. Explain example pipeline from Python subprocess module

Leave a Comment