Skip to content

Pylint throws exception for unexpected keyword argument when running prospector. #266

@justke86

Description

@justke86

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:

Traceback (most recent call last):
  File "<redacted>/bin/prospector", line 11, in <module>
    sys.exit(main())
  File "<redacted>/lib/python3.6/site-packages/prospector/run.py", line 173, in main
    prospector.execute()
  File "<redacted>/lib/python3.6/site-packages/prospector/run.py", line 53, in execute
    for tool in self.config.get_tools(found_files):
  File "<redacted>/python3.6/site-packages/prospector/config/__init__.py", line 45, in get_tools
    config_result = tool.configure(self, found_files)
  File "<redacted>/python3.6/site-packages/prospector/tools/pylint/__init__.py", line 185, in configure
    config_messages += self._pylintrc_configure(pylintrc, linter)
  File "<redacted>/lib/python3.6/site-packages/prospector/tools/pylint/__init__.py", line 103, in _pylintrc_configure
    are_plugins_loaded = linter.config_from_file(pylintrc)
  File "<redacted>/lib/python3.6/site-packages/prospector/tools/pylint/linter.py", line 24, in config_from_file
    self.read_config_file(config_file, quiet=True)
TypeError: read_config_file() got an unexpected keyword argument 'quiet'

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 argument quiet prior to it being updated to be verbose instead within pylint. This can be found in this commit: pylint-dev/pylint@49c6da5#diff-ade2cfcf3e840a993dbd465f517d91f5.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions