Releases: prospector-dev/prospector
1.8.1
Add support for Python 3.11
1.8.0
File discovery fixes:
Finding paths and files to check has been replaced with a new version using pathlib
- this should not result in any changes,
except fixing an issue where pylint
and pydocstyle
were inspecting the same file or directory twice sometimes.
However it may cause slightly different orders or reduce these duplicate warnings.
The behavior of prospector should be unchanged, apart from some bugfixes related to the old file discovery mechanism.
Related bugs and PRs:
Other bugfixes:
- #106
- Running prospector on a path not in the CWD (eg, 'prospector /some/where/else') will not cause exceptions, and will instead use absolute paths for message output
- Autodetction of libraries, to automatically use pylint plugins, will no work on projects using a pyproject.toml ; also it has been turned on by default, it seemed to have accidentally been set to off by default some time ago.
- #529
Misc:
- Prospector now runs on itself without generating errors after all linting warnings were fixed
1.8.0 rc1
1.8.0 rc0
This is currently still a pre-release.
File discovery fixes
Finding paths and files to check has been replaced with a new version using pathlib
- this should not result in any changes, except fixing an issue where pylint
and pydocstyle
were inspecting the same file or directory twice sometimes. However it may cause slightly different orders or reduce these duplicate warnings.
The behaviour of prospector should be unchanged, apart from some bugfixes related to the old file discovery mechanism.
Related bugs and PRs:
Other bugfixes
Misc
Prospector now runs on itself without generating errors after all linting warnings were fixed
1.7.7
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
andpep257
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 of1
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 previouspycodestyle
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