Bump prospector from 1.2.0 to 1.7.7

[dependabot]

Bumps prospector from 1.2.0 to 1.7.7.

Release notes

Sourced from prospector's releases.

1.7.7

Tiny bugfix relaese: restored __main__.py so that prospector could be run as a module, ie python -m prospector - #497

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.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

... (truncated)

Changelog

Sourced from prospector's changelog.

Version 1.7.7

Fixes:

• Restored __main__.py so that prospector could be run as a module, ie python -m prospector - [#497](https://github.com/PyCQA/prospector/issues/497) <https://github.com/PyCQA/prospector/pull/497>_

Version 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.

Version 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 <https://prospector.landscape.io/en/master/profiles.html#inheritance>. Closes [#161](https://github.com/PyCQA/prospector/issues/161) <https://github.com/PyCQA/prospector/issues/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](https://github.com/PyCQA/prospector/issues/455) <https://github.com/PyCQA/prospector/issues/455>_

Tidyup:

• Lots of warnings fixed from running prospector on itself

Version 1.7.4

Mea culpa release

Fix

The effort to allow pylint configuration in pyproject.toml to be used as an external config source (issue here <https://github.com/PyCQA/prospector/issues/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](https://github.com/PyCQA/prospector/issues/227) <https://github.com/PyCQA/prospector/issues/227>_.

... (truncated)

Commits

• 15b6317 Bumping version for 1.7.7 release
• 8f0d221 Merge pull request #497 from michaeltinsley/develop
• 6dcc8fb [pre-commit.ci] pre-commit autoupdate (#495)
• e5935df Fixing documentation about additional_requirements
• d93fbce Removed some flaky tests
• 526aa62 is_relative_to is not available for python < 3.9 so add a backwards compat me...
• 430e306 Fixed a problem where pylint was reporting the same message multiple times, b...
• 89c7a50 Tidying up some linting warnings
• c14444a Bumping version for next WIP release
• b02a436 Actually updating blender combinations this time
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #100.