pylint Cannot import custom module and function (no-name-in-module)

Question

I have the structure:

 |- file run_app.py

 |- folder 'tasks'

 |-- file app.py

There is a string in run_app.py:

import tasks.app

And pylint alerts that

run_app.py:8:0: E0611: No name 'app' in module 'tasks' (no-name-in-module)

When I rename tasks to taskss, the error disappears. Whats this? How to fix this strange behavior if I want to name the folder exactly 'tasks'?

I am not sure: python Python 3.6.6 (default, Sep 12 2018, 18:26:19) [GCC 8.0.1 20180414 (experimental) [trunk revision 259383]] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import tasks Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'tasks' >>> — sanyassh, Nov 01 '18 at 20:45
can you try: `from tasks import app`? have you also included an `init` in the folder named `tasks` ? — seralouk, Nov 01 '18 at 20:48
see alos this concerning the `init` file: https://stackoverflow.com/a/448279/5025009 — seralouk, Nov 01 '18 at 20:49

score 5 · Answer 1 · edited May 19 '20 at 21:39

Just to add to @makis answer: __init__.py were required to make a folder a package until python 3.2:

package_name/
  __init__.py <- makes package_name a package
  foo.py

But if you are in Python 3.3+ using __init__.py that way may generate pylint "no name in module" error:

package_name/
  __init__.py
  foo.py
  subpackage/
    other.py

from package_name.subpackage import other will generate the mentioned error.
If you remove that __init__.py, pylint stops warning you.

seralouk · Accepted Answer · 2020-04-02T16:45:46.520

3

Try to include an __init__.py file in the folder.

Reason:

The __init__.py files are required to make Python treat the directories as containing packages.

Structure:

package_name/
  __init__.py
  foo.py
  subpackage/
    other.py

edited Apr 02 '20 at 16:45

answered Nov 01 '18 at 20:55

seralouk

2 Answers2