no linting when using --init-hook in the parameter field
NicolasTriquenaux opened this issue · comments
Step 1: Are you in the right place?
- I have verified there are no duplicate active or recent bugs, questions, or requests
- I have verified that I am using the latest version of the plugin.
Step 2: Describe your environment
- Plugin version:
0.11.0 - PyCharm/IDEA version:
PyCharm 2018.3.4 (Community Edition) Build #PC-183.5429.31, built on January 29, 2019 macOS 10.14.3 - Pylint version:
pylint 1.9.4, astroid 1.6.5 Python 2.7.10 (default, Aug 17 2018, 19:45:58)
Step 3: Describe the problem:
Steps to reproduce:
- Set the
--init-hook='import sys; sys.path.extend(["path1", "path2"])'in the argument field (i do have a path to a pylint rc file set if it is of any use.)
Observed Results:
- The module output says that there is no problems (when there should) but no error whatsoever un pycharm logs. So i suspect that the scan is not run due to an uncaught error
Expected Results:
- I expected errors/warning out of the pylint analysis. Furthermore, if the --init-hook is not specified in the argument field, the scan is run (with some import-error i was trying to solve using the --init-hook option). If it is of any use, setting the init-hook inside the rc file works fine.
Screenshot of the failing configuration :
I did some investigating. So if you specify anything with quotes (" or ') in the Arguments field something crashes and is uncaught but the pylint runner class. I set up a watch on the pylint executions and none is run.
This issue has been automatically marked as stale because it has not had activity in the last 60 days.