-------------
This is mostly a "tidying up" release but some things have changed which may cause differences to output, hence the bump of the major version.
**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 <https://github.com/PyCQA/prospector/issues/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 internals**
These are all internal prospector code quality improvements. Ideally, they should not be noticed by anybody as they are internal refactorings.
* `467 <https://github.com/PyCQA/prospector/issues/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)
* Replaced `os.path` with `pathlib.Path` everywhere in prospector internals, to improve and simplify finding files to inspect. Theoretically this behaves in the same way as far as the user will see (please open a ticket if you notice anything obviously different)