1.7.6

It's a bugs life.

Fixes:

• Fixed a problem where pylint was reporting the same message multiple times, because it was given a path to the file multiple times
• The blending fix mentioned in the 1.7.5 release was actually not checked in by accident, this is there now.

1.7.5

Just say no to bugs.

New:

• Profile inheritance is now optional - appending a profile name with a ? means that if it is not found, prospector will simply continue. Read the documentation here. Closes #161

Fixes:

• Stopped the ProfileValidator tool raising errors about pep8 and pep257 sections being unknown. Instead, they raise deprecated warnings.
• Blending works again - for example, pylint and pycodestyle errors representing the same thing are combined. After renaming pep8 to pycodestyle, this only worked when using legacy names.
• Unrecognised Mypy options now raise an exception instead of silently carrying on - #455

Tidyup:

• Lots of warnings fixed from running prospector on itself

1.7.4

Mea culpa release

Fix

The effort to allow pylint configuration in pyproject.toml to be used as an external config source (#485) had the unintended side effect where any project using poetry would now use that configuration and thus would ignore the pylint configuration in the profile. This was true even if the pyproject.toml had no pylint directives in it.

The behaviour has now been fixed where pylint will be configured using configuration from the profile first and then if any additional settings are found in a pylintrc or pyproject.toml or setup.cfg then these will override the profile configuration, instead of replacing it entirely.

This also has the benefit of fixing #227 .

1.7.3 [yanked from PyPI, see 1.7.4]

The war on bugs.

Fixes:

• Autodetect now does not die if a user does not have permissions (related to #271 and #487)
• Fixed that some pylint documentation warning messages were not correctly included in the list of documentation warnings to squash if doc warnings are not desired.
• Fixed the exit code for prospector - it was always 0 after the move to using poetry for packaging instead of 1 if errors were found (unless --zero-exit) was used. This now exits with the correct code based on the documented (and previous) behaviour.
• Fix that pep8 would overwrite instead of inherit from previous pycodestyle blocks, same with pep257 - #491
• Fix the pre-commit hook, as it could not run without being installed [with_everything], due to the "NotAvailableTool" class not properly implementing the abstract base class.
• Improved documentation about the pre-commit hook as well to clarify its use better - #484

Version 1.7.2 [yanked from PyPI, see 1.7.4]

More bugfixes!

Fixes:

• Fix that pep8 and pep257 sections were renamed but the old deprecated values were not properly used to configure pycodestyle and pydocstyle - #491
• Better handling for when the user running prospector is not able to read a file or directory - #271 and #487

1.7.1

Lots of smaller bugfixes in this release.

Fixes:

• Prospector now configures pylint using settings found in pyproject.toml or setup.cfg, not only .pylintrc - #485
• Fixed --no-style-warnings command line argument no longer warning after renaming pep8 to pycodestyle - #488
• Documentation is building again - #473
• --with-tool flag now respects - but overrides - tools disabled in profiles - #447
• Fixed crash with merging multiple import warnings - #477
• Fixed segfault when analysing code using cartopy - #403

1.7.0

This is mostly a "tidying up" release in preparation for more useful code refactoring and feature improvement.

New:

• Added a --quiet command line option to suppress all output. Useful if you just want to know the exit code of prospector for scripting.
• Removed the prospector "indent checker" since this is now no longer in pylint #482 <https://github.com/PyCQA/prospector/issues/482>_

Fixes:

Deprecation warning:

• Tools pep8 and pep257 have been renamed to pycodestyle and pydocstyle respectively. This is because the tools themselves were renamed years ago - See #222.
  Note that this means that prospector profiles and message output uses this new name instead of the old name, so you will need to update your configuration. The old names will still work, but this legacy behaviour will be removed in prospector 2.0
• There is now a --legacy-tool-names flag for outputting pep8 or pep257 as the tool name when outputting errors. This is to be backwards compatible with any parsing logic; this flag is also deprecated and will go away in prospector 2.0

Tidying up

These are all internal prospector code quality improvements.

• #467 - Removed nosetests, as nose is not compatible with Python 3.10 yet and the pytest tests were already doing the same thing
• Tidied up the tox testing
• Started adding some type hints to methods
• Fixed lots of warnings raised by prospector when running prospector on itself...
• Removed some old python2 compatibility code which is no longer needed now python2 is not supported at all
• Fixed hyperlink formatting in this CHANGELOG to be RST (was never updated after converting from markdown)

1.6.0

• #478 Fixed incompatible version specification of pylint-plugin-utils. This
  now requires pylint-django of at least 2.5.

note This release drops support for python 3.6.1

1.5.3.1

Removed pin for pylint

1.5.3

Bugfix release to fix compatibility with latest version of pylint - #465