Pylint not respecting toml/rc config
See original GitHub issueHi,
When i use flakeheaven with pylint, and i try and set in either the pyproject.toml or a supplied toml to flakeheaven lint --config=myconfig.toml file1
the following:
[tool.pylint.'MASTER']
load-plugins = ["pylint_pytest", "perflint"]
max-line-length = 10
With the 10 just to trigger errors - it doesn’t work. Same when I put a pylintrc file in the same dir. This seems to be because you are using the import pylint version of things - is that possible?
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:11
Top Results From Across the Web
Pylint can't read the configuration file if there is unrecognised ...
I cannot reproduce this using the latest code from the master branch. What I did: created a setup.cfg file, with the following content:...
Read more >Settings for pylint in setup.cfg are not getting used
pylintrc in the current directory and pyproject.toml doesn't contain any tool.pylint. section. However, the following settings in setup.cfg don' ...
Read more >Running Pylint - Pylint 2.16.0-dev documentation
Pylint will not import this package or module, but it does use Python internals to locate them and as such is subject to...
Read more >Pylint configuration - CodeFlow
Pylint requires configuration via a .pylint configuration file as detailed in Pylint's ... They should be base names, not # paths. ignore=CVS #...
Read more >Pylint configuration - Codeac
Pylint requires configuration via a .pylint configuration file as detailed in Pylint's ... They should be base names, not # paths. ignore=CVS #...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Worked 😄
Hey guys, I just ran into this as well. We tracked the problem down to a ~/.pylintrc (in the home directory) that pylint was picking up on.
If i have time over the weekend, I will try to get a pull request put together so that we add the extra option “–rcfile” to the args of pylint, so that we can override the default resolution, and then get back deterministic execution of pylint.
In the mean time, look for a ~/.pylintrc, and remove it if you can, to at least get around the problem in the mean time