Ошибка unable to import

If you want to walk up from the current module/file that was handed to pylint looking for the root of the module, this will do it.

[MASTER]
init-hook=sys.path += [os.path.abspath(os.path.join(os.path.sep, *sys.argv[-1].split(os.sep)[:i])) for i, _ in enumerate(sys.argv[-1].split(os.sep)) if os.path.isdir(os.path.abspath(os.path.join(os.path.sep, *sys.argv[-1].split(os.sep)[:i], '.git')))][::-1]

If you have a python module ~/code/mymodule/, with a top-level directory layout like this

~/code/mymodule/
├── .pylintrc
├── mymodule/
│   └── src.py
└── tests/
    └── test_src.py

Then this will add ~/code/mymodule/ to your python path and allow for pylint to run in your IDE, even if you’re importing mymodule.src in tests/test_src.py.

You could swap out a check for a .pylintrc instead but a git directory is usually what you want when it comes to the root of a python module.

Before you ask

The answers using import sys, os; sys.path.append(...) are missing something that justifies the format of my answer. I don’t normally write code that way, but in this case you’re stuck dealing with the limitations of the pylintrc config parser and evaluator. It literally runs exec in the context of the init_hook callback so any attempt to import pathlib, use multi-line statements, store something into variables, etc., won’t work.

A less disgusting form of my code might look like this:

import os
import sys

def look_for_git_dirs(filename):
    has_git_dir = []
    filename_parts = filename.split(os.sep)
    for i, _ in enumerate(filename_parts):
        filename_part = os.path.abspath(os.path.join(os.path.sep, *filename_parts[:i]))
        if os.path.isdir(os.path.join(filename_part, '.git')):
            has_git_dir.append(filename_part)
    return has_git_dir[::-1]

# don't use .append() in case there's < 1 or > 1 matches found
sys.path += look_for_git_dirs(sys.argv[-1])

I wish I could have used pathlib.Path(filename).parents it would have made things much easier.

IgorDV
Модуль импортируется, доступ к содержимому есть.
И все равно подчеркивает import — Unable to import ‘util_date’pylint(import-error)

Ну это сугубо ограничения IDE.
Вы же понимаете, что для того, чтобы правильно импортировать модуль util_date надо выполнить код?
Вот эта ваша строка

 sys.path.append(os.path.join(sys.path, ‘..util’))

должна быть выполнена перед импортом. Это не магия, не специальный синтаксис, это обычный вызов функции в питоне.
А теперь подумайте, а откуда IDE должна знать, что пути к библиотеке меняются по ходу выполнения программы? Откуда она знает, что вы вызываете функцию, которая добавляет путь к каталогу вашего модуля? Вы подразумеваете, что IDE выполняет код, который читает. Это было бы вообще говоря довольно опасное поведение, давайте представим, что мы пишем программу, котоая удаляет все файлы из домашней директории. И вот мы написали программу, а ИДЕ взяла и без спроса её выполнила.
Ну и вообще, кто мешает написать вот такой код

 if DEVELOP:
    sys.path.append(os.path.join(sys.path, 'develop',  'util'))
elif PRODUCTION:
    sys.path.append(os.path.join(sys.path, 'prod',  'util'))
elif TEST:
    .....

И как ваша ИДЕ должна определить, какой именно модуль вы собрались поключать?

1. Unable to import (pylint)

• Scenario: You have a module installed, however the linter in the IDE is complaining about; not being able to import the module, hence error messages such as the following are displayed as linter errors:

.. unable to import 'xxx' .. 

• Cause: The Python extension is most likely using the wrong version of Pylint.

Solution 1: (configure workspace settings to point to fully qualified python executable):

1. Open the workspace settings (settings.json)
2. Identify the fully qualified path to the python executable (this could even be a virtual environment)
3. Ensure Pylint is installed for the above python environment
4. Configure the setting “pythonPath” to point to (previously identified) the fully qualified python executable.

"python.pythonPath": "/users/xxx/bin/python"

Solution 2: (open VS Code from an activated virtual environment):

1. Open the terminal window
2. Activate the relevant python virtual environment
3. Ensure Pylint is installed within this virtual environment pip install pylint
4. Close all instances of VS Code
5. Launch VS Code from within this terminal window
   (this will ensure the VS Code process will inherit all of the Virtual Env environment settings)

2. Linting with xxx failed. …

Listing could fail due to a number of reasons. Please check each of the following.

Cause: The path to the python executable is incorrect
Solution: Configure the path to the python executable in the settings.json

Cause: The linter has not been installed in the Python environment being used
Solution: Identify the Python environment (executable) configured in settings.json. Next install the linter(s) against this Python environment (use the corresponding Pip).

Cause: The Path to the linter is incorrect
Solution: If you have provided a custom path to the linter in settings.json, then ensure this file path exist.

For further information on configuring Linters can be found here.

3. Ignore certain messages

It is possible you would like to ignore certain linter messages. This could be done easily.
Generally most linters support configuration files, hence all you need to do is create the relevant configuration file and ignore the appropriate error message.
If on the other hand the linters support the ability to ignore certain messages via command line args, this can be done as well.

Solution: Add relevant command line args to ignore certain messages
Here we’ll assume you use a TAB character as indentation of python code instead of 4 or 2 spaces.
Pylint would generally display a warning for this with the error code W0312.
In order to disable this particular message all one needs to do is as follows in the settings.json file:

 "python.linting.pylintArgs": [
        "--disable=W0312"
 ],

Note: You could apply the above configuration settings in your user settings file, so that it applies to all workspaces.
This saves you from having to define these settings for every single workspace (every time).

For further information on configuring Linters can be found here.

Вопрос:

__init__.py
myapp.py
one.py
subdir
__init__.py
two.py

F0401: Unable to import 'one'

Ответ №1

[MASTER]
init-hook='import sys; sys.path.append("/path/to/root")'

Ответ №2

[Master]
init-hook='sys.path = ["/path/myapps/bin/", "/path/to/myapps/lib/python3.3/site-packages/", ... many paths here])'

[Master]
init-hook='sys.path = list(); sys.path.append("/path/to/foo")'

pylint --rcfile /path/to/pylintrc /path/to/module.py

Ответ №3

[MASTER]
init-hook="from pylint.config import find_pylintrc; import os, sys; sys.path.append(os.path.dirname(find_pylintrc()))"

Ответ №4

topdir
__init__.py
functions_etc.py
subdir
__init__.py
other_functions.py

Ответ №5

{
"python.pythonPath": "venv/bin/python",
"python.linting.pylintPath": "venv/bin/pylint"
}

Ответ №6

PYTHONPATH=${PYTHONPATH}:$(dirname %d) pylint --output-format=parseable --reports=n "%f"

Ответ №7

Ответ №8

Один обходной путь, который я только что открыл, – это просто запустить PyLint для всего пакета, а не только одного файла. Так или иначе, ему удастся найти импортированный модуль.

Ответ №9

if __name__ == '__main__':
    from [whatever the name of your package is] import one
else:
    import one

from .. import one

if __name__ == '__main__':
    from [whatever the name of your package is] import one   # assuming the package is in the current working directory or a subdirectory of PYTHONPATH
else:
    from .. import one

import os

olddir = os.getcwd()
os.chdir([path_of_directory_containing_module_one])
import one
os.chdir(olddir)

Ответ №10

[MASTER]
init-hook='base_dir="my_spider"; import sys,os,re; _re=re.search(r".+/" + base_dir, os.getcwd()); project_dir = _re.group() if _re else os.path.join(os.getcwd(), base_dir); sys.path.append(project_dir)'

Ответ №11

[Master]
init-hook='sys.path = list(); sys.path.append("./Lib/site-packages/")'

Ответ №12

sys.path.append(dirname)

Ответ №13

;;;;;;;;;;;;;;;;;
;; PYTHON PATH ;;
;;;;;;;;;;;;;;;;;

(defun python-expand-path ()
"Append a directory to the PYTHONPATH."
(interactive
(let ((string (read-directory-name
"Python package directory: "
nil
'my-history)))
(setenv "PYTHONPATH" (concat (expand-file-name string)
(getenv ":PYTHONPATH"))))))

(defun pythonpath-dired-mode-hook ()
(let ((setup_py (concat default-directory "setup.py"))
(directory (expand-file-name default-directory)))
;;   (if (file-exists-p setup_py)
(if (is-python-package-directory directory)
(let ((pythonpath (concat (getenv "PYTHONPATH") ":"
(expand-file-name directory))))
(setenv "PYTHONPATH" pythonpath)
(message (concat "PYTHONPATH=" (getenv "PYTHONPATH")))))))

(defun is-python-package-directory (directory)
(let ((setup_py (concat directory "setup.py")))
(file-exists-p setup_py)))

(add-hook 'dired-mode-hook 'pythonpath-dired-mode-hook)

Ответ №14

Ответ №15

Я нашел хороший ответ от https://sam.hooke.me/note/2019/01/call-python-script-from-pylint-init-hook/
отредактируйте ваш pylintrc и добавьте следующее в master init-hook="import imp, os; from pylint.config import find_pylintrc; imp.load_source('import_hook', os.path.join(os.path.dirname(find_pylintrc()), 'import_hook.py'))"

Ответ №16

если вы используете vscode, убедитесь, что каталог вашего пакета находится вне каталога _pychache__.

Ответ №17

from .. import one

Ответ №18

Если вы используете Cython в Linux, я решил удалить файлы module.cpython-XXm-X-linux-gnu.so из целевой директории моего проекта.

Ответ №19

Environment data

• VS Code version: 1.20.0
• Extension version (available under the Extensions sidebar): 2018.2.1
• OS and version: macOS Sierra version 10.12.6
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda custom (64 bit) Python 3.6.4
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda
• Relevant/affected Python packages and their versions:

Actual behavior

This program works fine from the command line. I wrote this using the Python extension approx. 6 months ago on another mac. I recently picked up this program again and it shows me the import errors as shown in the attached screenshot. I know that it is pylint related. I am also attaching my user settings and workspace settings screenshots

Expected behavior

It should not show errors for import

Steps to reproduce:

See the screenshorts

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

6,0,error,E0401:Unable to import ‘vglabs_common’
7,0,error,E0401:Unable to import ‘vglabs_anis’
8,0,error,E0401:Unable to import ‘vglabs_brz’
10,0,error,E0401:Unable to import ‘vglabs_inf’
11,0,error,E0401:Unable to import ‘vglabs_mrp’
12,0,error,E0401:Unable to import ‘vglabs_nmr’
13,0,error,E0401:Unable to import ‘vglabs_op’
14,0,error,E0401:Unable to import ‘vglabs_re’
15,0,error,E0401:Unable to import ‘vglabs_ssk’
16,0,error,E0401:Unable to import ‘vglabs_txc’
17,0,error,E0401:Unable to import ‘vglabs_xrd’
##########Linting Output — pylint##########
No config file found, using default configuration
************* Module vglabs_uploader
6,0,error,E0401:Unable to import ‘vglabs_common’
7,0,error,E0401:Unable to import ‘vglabs_anis’
8,0,error,E0401:Unable to import ‘vglabs_brz’
10,0,error,E0401:Unable to import ‘vglabs_inf’
11,0,error,E0401:Unable to import ‘vglabs_mrp’
12,0,error,E0401:Unable to import ‘vglabs_nmr’
13,0,error,E0401:Unable to import ‘vglabs_op’
14,0,error,E0401:Unable to import ‘vglabs_re’
15,0,error,E0401:Unable to import ‘vglabs_ssk’
16,0,error,E0401:Unable to import ‘vglabs_txc’
17,0,error,E0401:Unable to import ‘vglabs_xrd’
59,0,refactor,R0912:Too many branches (15/12)
107,0,refactor,R0912:Too many branches (15/12)
5,0,warning,W0611:Unused import psycopg2
XXX

Output from `Console` under the `Developer Tools` panel (toggle Developer Tools on under `Help`)

XXX

Пытаться

if __name__ == '__main__':
    from [whatever the name of your package is] import one
else:
    import one

Обратите внимание, что в Python 3 синтаксис для части в else пункт будет

from .. import one

Если подумать, это, вероятно, не решит вашу конкретную проблему. Я неправильно понял вопрос и подумал, что two.py запускается как основной модуль, но это не так. И учитывая различия в способах Python 2.6 (без импорта absolute_import от __future__) и Python 3.x обрабатывают импорт, вам в любом случае не нужно делать это для Python 2.6, я не думаю.

Тем не менее, если вы в конечном итоге переключитесь на Python 3 и планируете использовать модуль как в качестве модуля пакета, так и в качестве автономного скрипта внутри пакета, может быть хорошей идеей сохранить что-то вроде

if __name__ == '__main__':
    from [whatever the name of your package is] import one   # assuming the package is in the current working directory or a subdirectory of PYTHONPATH
else:
    from .. import one

в виду.

РЕДАКТИРОВАТЬ: А теперь о возможном решении вашей реальной проблемы. Либо запустите PyLint из каталога, содержащего ваш one модуль (возможно, через командную строку) или поместите где-нибудь следующий код при запуске PyLint:

import os

olddir = os.getcwd()
os.chdir([path_of_directory_containing_module_one])
import one
os.chdir(olddir)

По сути, в качестве альтернативы возиться с PYTHONPATH просто убедитесь, что текущий рабочий каталог — это каталог, содержащий one.py когда вы делаете импорт.

(Глядя на ответ Брайана, вы, вероятно, могли бы присвоить предыдущий код init_hook, но если вы собираетесь это сделать, вы можете просто добавить к sys.path что он делает, что немного более элегантно, чем мое решение.)

1. Unable to import (pylint)

• Scenario: You have a module installed, however the linter in the IDE is complaining about; not being able to import the module, hence error messages such as the following are displayed as linter errors:

.. unable to import 'xxx' .. 

• Cause: The Python extension is most likely using the wrong version of Pylint.

Solution 1: (configure workspace settings to point to fully qualified python executable):

1. Open the workspace settings (settings.json)
2. Identify the fully qualified path to the python executable (this could even be a virtual environment)
3. Ensure Pylint is installed for the above python environment
4. Configure the setting “pythonPath” to point to (previously identified) the fully qualified python executable.

"python.pythonPath": "/users/xxx/bin/python"

Solution 2: (open VS Code from an activated virtual environment):

1. Open the terminal window
2. Activate the relevant python virtual environment
3. Ensure Pylint is installed within this virtual environment pip install pylint
4. Close all instances of VS Code
5. Launch VS Code from within this terminal window
   (this will ensure the VS Code process will inherit all of the Virtual Env environment settings)

2. Linting with xxx failed. …

Listing could fail due to a number of reasons. Please check each of the following.

Cause: The path to the python executable is incorrect
Solution: Configure the path to the python executable in the settings.json

Cause: The linter has not been installed in the Python environment being used
Solution: Identify the Python environment (executable) configured in settings.json. Next install the linter(s) against this Python environment (use the corresponding Pip).

Cause: The Path to the linter is incorrect
Solution: If you have provided a custom path to the linter in settings.json, then ensure this file path exist.

For further information on configuring Linters can be found here.

3. Ignore certain messages

It is possible you would like to ignore certain linter messages. This could be done easily.
Generally most linters support configuration files, hence all you need to do is create the relevant configuration file and ignore the appropriate error message.
If on the other hand the linters support the ability to ignore certain messages via command line args, this can be done as well.

Solution: Add relevant command line args to ignore certain messages
Here we’ll assume you use a TAB character as indentation of python code instead of 4 or 2 spaces.
Pylint would generally display a warning for this with the error code W0312.
In order to disable this particular message all one needs to do is as follows in the settings.json file:

 "python.linting.pylintArgs": [
        "--disable=W0312"
 ],

Note: You could apply the above configuration settings in your user settings file, so that it applies to all workspaces.
This saves you from having to define these settings for every single workspace (every time).

For further information on configuring Linters can be found here.

Linting

1. Unable to import (pylint)

• Scenario: You have a module installed, however the linter in the IDE is complaining about; not being able to import the module, hence error messages such as the following are displayed as linter errors:

• Cause: The Python extension is most likely using the wrong version of Pylint.

Solution 1: (configure workspace settings to point to fully qualified python executable):

1. Open the workspace settings (settings.json)
2. Identify the fully qualified path to the python executable (this could even be a virtual environment)
3. Ensure Pylint is installed for the above python environment
4. Configure the setting “pythonPath” to point to (previously identified) the fully qualified python executable.

Solution 2: (open VS Code from an activated virtual environment):

1. Open the terminal window
2. Activate the relevant python virtual environment
3. Ensure Pylint is installed within this virtual environment pip install pylint
4. Close all instances of VS Code
5. Launch VS Code from within this terminal window
   (this will ensure the VS Code process will inherit all of the Virtual Env environment settings)

2. Linting with xxx failed. …

Listing could fail due to a number of reasons. Please check each of the following.

Cause: The path to the python executable is incorrect
Solution: Configure the path to the python executable in the settings.json

Cause: The linter has not been installed in the Python environment being used
Solution: Identify the Python environment (executable) configured in settings.json. Next install the linter(s) against this Python environment (use the corresponding Pip).

Cause: The Path to the linter is incorrect
Solution: If you have provided a custom path to the linter in settings.json, then ensure this file path exist.

For further information on configuring Linters can be found here.

3. Ignore certain messages

It is possible you would like to ignore certain linter messages. This could be done easily.
Generally most linters support configuration files, hence all you need to do is create the relevant configuration file and ignore the appropriate error message.
If on the other hand the linters support the ability to ignore certain messages via command line args, this can be done as well.

Solution: Add relevant command line args to ignore certain messages
Here we’ll assume you use a TAB character as indentation of python code instead of 4 or 2 spaces. Pylint would generally display a warning for this with the error code W0312.
In order to disable this particular message all one needs to do is as follows in the settings.json file:

Note: You could apply the above configuration settings in your user settings file, so that it applies to all workspaces.
This saves you from having to define these settings for every single workspace (every time).

For further information on configuring Linters can be found here.

Linting

1. Unable to import (pylint)

• Scenario: You have a module installed, however the linter in the IDE is complaining about; not being able to import the module, hence error messages such as the following are displayed as linter errors:

• Cause: The Python extension is most likely using the wrong version of Pylint.

Solution 1: (configure workspace settings to point to fully qualified python executable):

1. Open the workspace settings (settings.json)
2. Identify the fully qualified path to the python executable (this could even be a virtual environment)
3. Ensure Pylint is installed for the above python environment
4. Configure the setting “pythonPath” to point to (previously identified) the fully qualified python executable.

Solution 2: (open VS Code from an activated virtual environment):

1. Open the terminal window
2. Activate the relevant python virtual environment
3. Ensure Pylint is installed within this virtual environment pip install pylint
4. Close all instances of VS Code
5. Launch VS Code from within this terminal window
   (this will ensure the VS Code process will inherit all of the Virtual Env environment settings)

2. Linting with xxx failed. …

Listing could fail due to a number of reasons. Please check each of the following.

Cause: The path to the python executable is incorrect
Solution: Configure the path to the python executable in the settings.json

Cause: The linter has not been installed in the Python environment being used
Solution: Identify the Python environment (executable) configured in settings.json. Next install the linter(s) against this Python environment (use the corresponding Pip).

Cause: The Path to the linter is incorrect
Solution: If you have provided a custom path to the linter in settings.json, then ensure this file path exist.

For further information on configuring Linters can be found here.

3. Ignore certain messages

It is possible you would like to ignore certain linter messages. This could be done easily.
Generally most linters support configuration files, hence all you need to do is create the relevant configuration file and ignore the appropriate error message.
If on the other hand the linters support the ability to ignore certain messages via command line args, this can be done as well.

Solution: Add relevant command line args to ignore certain messages
Here we’ll assume you use a TAB character as indentation of python code instead of 4 or 2 spaces. Pylint would generally display a warning for this with the error code W0312.
In order to disable this particular message all one needs to do is as follows in the settings.json file:

Note: You could apply the above configuration settings in your user settings file, so that it applies to all workspaces.
This saves you from having to define these settings for every single workspace (every time).

For further information on configuring Linters can be found here.

Источник

Linting Python in Visual Studio Code

Linting highlights syntactical and stylistic problems in your Python source code, which often helps you identify and correct subtle programming errors or unconventional coding practices that can lead to errors. For example, linting detects use of an uninitialized or undefined variable, calls to undefined functions, missing parentheses, and even more subtle issues such as attempting to redefine built-in types or functions. Linting is thus distinct from Formatting because linting analyzes how the code runs and detects errors whereas formatting only restructures how code appears.

Note: Stylistic and syntactical code detection is enabled by the Language Server. To enable third-party linters for additional problem detection, you can enable them by using the Python: Select Linter command and selecting the appropriate linter.

Enable linting

To enable linters, open the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ) and select the Python: Select Linter command. The Select Linter command adds «python.linting.

Environment data

• VS Code version: 1.20.0
• Extension version (available under the Extensions sidebar): 2018.2.1
• OS and version: macOS Sierra version 10.12.6
• Python version (& distribution if applicable, e.g. Anaconda): Anaconda custom (64 bit) Python 3.6.4
• Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda
• Relevant/affected Python packages and their versions:

Actual behavior

This program works fine from the command line. I wrote this using the Python extension approx. 6 months ago on another mac. I recently picked up this program again and it shows me the import errors as shown in the attached screenshot. I know that it is pylint related. I am also attaching my user settings and workspace settings screenshots

Expected behavior

It should not show errors for import

Steps to reproduce:

See the screenshorts

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

6,0,error,E0401:Unable to import ‘vglabs_common’
7,0,error,E0401:Unable to import ‘vglabs_anis’
8,0,error,E0401:Unable to import ‘vglabs_brz’
10,0,error,E0401:Unable to import ‘vglabs_inf’
11,0,error,E0401:Unable to import ‘vglabs_mrp’
12,0,error,E0401:Unable to import ‘vglabs_nmr’
13,0,error,E0401:Unable to import ‘vglabs_op’
14,0,error,E0401:Unable to import ‘vglabs_re’
15,0,error,E0401:Unable to import ‘vglabs_ssk’
16,0,error,E0401:Unable to import ‘vglabs_txc’
17,0,error,E0401:Unable to import ‘vglabs_xrd’
##########Linting Output — pylint##########
No config file found, using default configuration
************* Module vglabs_uploader
6,0,error,E0401:Unable to import ‘vglabs_common’
7,0,error,E0401:Unable to import ‘vglabs_anis’
8,0,error,E0401:Unable to import ‘vglabs_brz’
10,0,error,E0401:Unable to import ‘vglabs_inf’
11,0,error,E0401:Unable to import ‘vglabs_mrp’
12,0,error,E0401:Unable to import ‘vglabs_nmr’
13,0,error,E0401:Unable to import ‘vglabs_op’
14,0,error,E0401:Unable to import ‘vglabs_re’
15,0,error,E0401:Unable to import ‘vglabs_ssk’
16,0,error,E0401:Unable to import ‘vglabs_txc’
17,0,error,E0401:Unable to import ‘vglabs_xrd’
59,0,refactor,R0912:Too many branches (15/12)
107,0,refactor,R0912:Too many branches (15/12)
5,0,warning,W0611:Unused import psycopg2
XXX

Output from `Console` under the `Developer Tools` panel (toggle Developer Tools on under `Help`)

XXX