prospector
prospector copied to clipboard
[BUG] --member-warnings does not seem to be working
Describe the bug
Pylint raises a no-name-in-module error. Prospector seems to be ignoring this, even when invoked with --member-warnings
To Reproduce
$ cat aaa.py
from pydantic import BaseModel
Running pylint:
$ pylint -E aaa.py
************* Module aaa
aaa.py:1:0: E0611: No name 'BaseModel' in module 'pydantic' (no-name-in-module)
Running prospector:
$ prospector --member-warnings -t pylint aaa.py
Messages
========
aaa.py
Line: 1
pylint: unused-import / Unused BaseModel imported from pydantic
Check Information
=================
Started: 2021-03-19 07:20:12.064294
Finished: 2021-03-19 07:20:12.488859
Time Taken: 0.42 seconds
Formatter: grouped
Profiles: default, member_warnings, no_doc_warnings, no_test_warnings, strictness_medium, strictness_high, strictness_veryhigh, no_member_warnings
Strictness: None
Libraries Used:
Tools Run: pylint
Messages Found: 1
Expected behavior Prospector should raise the error, too.
Environment (please complete the following information):
$ python --version
Python 3.8.6
$ poetry show prospector
name : prospector
version : 1.3.1
description : Prospector: python static analysis tool
dependencies
- astroid 2.4.1
- dodgy >=0.1.9
- mccabe >=0.5.0
- pep8-naming >=0.3.3,<=0.10.0
- pycodestyle >=2.6.0,<2.7.0
- pydocstyle >=2.0.0
- pyflakes >=2.2.0,<2.3.0
- pylint 2.5.3
- pylint-celery 0.3
- pylint-django <2.2.0
- pylint-flask 0.6
- pylint-plugin-utils >=0.2.6
- pyyaml *
- requirements-detector >=0.6
- setoptconf >=0.2.0
$ poetry show pydantic
name : pydantic
version : 1.8.1
description : Data validation and settings management using python 3.6 type hinting
dependencies
- dataclasses >=0.6
- typing-extensions >=3.7.4.3