Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Empty or Default .pylintrc results in "found no problems" #93

Open
fredlllll opened this issue Jul 28, 2022 · 3 comments
Open

Empty or Default .pylintrc results in "found no problems" #93

fredlllll opened this issue Jul 28, 2022 · 3 comments

Comments

@fredlllll
Copy link

fredlllll commented Jul 28, 2022

Step 1: Are you in the right place?

  • [ X ] I have verified there are no duplicate active or recent bugs, questions, or requests
  • [ X ] I have verified that I am using the latest version of the plugin.

Step 2: Describe your environment

  • Plugin version: 0.14.0
  • PyCharm/IDEA version: PyCharm 2022.2 (Windows 10)
  • Pylint version: 2.14.5

Step 3: Describe the problem:

Steps to reproduce:

  1. create empty or default .pylintrc file in project root
  2. run pylint

Observed Results:

  • get told there are no problems found, while there clearly are problems if run without the file present
  • it also runs much faster through the project

Expected Results:

  • same output as if no pylintrc file exists, or at least SOME errors

Relevant Code:

pycharm64_2022-07-28_17-55-36

and a run after deleting the empty pylintrc file

grafik

@Ralithune
Copy link

I just ran in to this, except my pylintrc file had pylint spewing errors about "options value for 'x' was removed from pylint" and then a link to the pull request that removed it.

Frustates me that the Pylint maintainers (not you) don't have clear instructions on how (or WHY?) the ignore statements were removed from Pylint and what we're supposed to do about it. This is not how I wanted to spend my day.

@kannes
Copy link

kannes commented Jan 6, 2023

Isn't this a duplicate of #69?

@fredlllll
Copy link
Author

possibly, although that issue uses older versions, runs on a mac, and the user has some custom hooks etc built into his environment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants