-
Notifications
You must be signed in to change notification settings - Fork 174
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
Pylint throws exception for unexpected keyword argument when running prospector. #266
Comments
Could you let me know what version of prospector + pylint you are running with a pip freeze? I think I fixed that in this commit just yesterday for version 1.0 - 13214a0 You will have to upgrade prospector and pylint. |
I'm currently using pipenv 2018.7.1, and here's the pipenv graph when running into this issue:
Here's the pip freeze info from within the virtual env:
I'm using python 3.6.3 and I think I have the latest pylint and prospector. |
Seems I must have misread the change when the |
Before pylint 2, it was called quiet but used in a different method ; I tried to make it work with old and new versions but missed that it was renamed in newer versions. Sorry about that. |
No problem, it happens, just figured I'd point it out so others don't run into similar issues, although from looking at your commit that you posted above, it looks like you may just need to move the |
You're welcome to make a PR ;-) I probably can't get on to this until tomorrow.
|
That's understandable, I was a little hesitant at first on the PR, but I gave it a shot: #267 |
Is there any update on this issue? |
Keeping this issue open until the fix is released. |
I also got this error on |
I still have this problem on prospector 1.1.2. Also using virtualenv. Here's my traceback:
|
Pull request #283 solves this issue. Looking at the Pylint history, the |
later versions have incorrect handling of 'quiet' flag for pylint<2 See prospector-dev/prospector#266
* fix length of config file name which could enable install on conda forge * update yapf and prospector * disable useless-object-inheritance warning cannot make pylint happy both in python2 and 3 * fix python3 warnings + try to upgrade versions * try fixing version updater split setup.py into setup.py and setup.json (logic was partly written for setup.json, was trying to load setup.py as json file) * fix package_data bug * try fixing install issues * include setup.json in manifest * switch to local prospector installation guykisel mirror was using v0.8 which was breaking pylint on py2.7 * fix prospector version later versions have incorrect handling of 'quiet' flag for pylint<2 See prospector-dev/prospector#266 * fix prospector verison * updated: remove obsolete setup_version_pat
@chocoelho Why did you close this issue? Please consider merging #283 and releasing a new version of prospector. |
I may have closed it by mistake, will merge some PRs today and release a
new prospector version later today.
Em quinta-feira, 15 de novembro de 2018, Leopold Talirz <
notifications@github.com> escreveu:
… @chocoelho <https://github.com/chocoelho> Why did you close this issue?
The issue persists (cannot use prospector with pylint <2), and there is a
PR open (#283 <#283>) to resolve
it.
I checked and confirm that this PR resolves the issue.
Please consider merging #283
<#283> and releasing a new
version of prospector.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#266 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADTNU60oOcY1qKqOv8AKCHlMAmzvrEYDks5uvaS0gaJpZM4VdLds>
.
|
Can you please test again with 1.1.5? |
@chocoelho Thanks a lot, works for me! |
I was running prospector using python 3.6 and the latest version of prospector, but when attempting to run it, it would just throw the following error:
From reading through the prospector codebase and the pylint codebase, it looks like the line
self.read_config_file(config_file, quiet=True)
is using the old keyword argumentquiet
prior to it being updated to beverbose
instead within pylint. This can be found in this commit: pylint-dev/pylint@49c6da5#diff-ade2cfcf3e840a993dbd465f517d91f5.The text was updated successfully, but these errors were encountered: