Prospector

Latest version: v1.10.3

Safety actively analyzes 629503 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 16

1.8.3

-------------

* `560 <https://github.com/PyCQA/prospector/issues/560>`_
* `559 <https://github.com/PyCQA/prospector/issues/559>`_
* `555 <https://github.com/PyCQA/prospector/issues/555>`_
* `554 <https://github.com/PyCQA/prospector/issues/554>`_
* `552 <https://github.com/PyCQA/prospector/issues/552>`_
* `551 <https://github.com/PyCQA/prospector/issues/551>`_

1.8.2

-------------

* `547 <https://github.com/PyCQA/prospector/issues/547>`_

1.8.1

-------------

Let's test faster.

**Add support for Python 3.11**:

Python 3.11 is between 10-60% faster than Python 3.10.

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:

* `480 <https://github.com/PyCQA/prospector/issues/480>`_
* `417 <https://github.com/PyCQA/prospector/issues/417>`_
* `199 <https://github.com/PyCQA/prospector/issues/199>`_

**Other bugfixes**:

* `106 <https://github.com/PyCQA/prospector/issues/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 <https://github.com/PyCQA/prospector/issues/529>`_

**Misc**:

* Prospector now runs on itself without generating errors after all linting warnings were fixed

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 <https://prospector.landscape.io/en/master/profiles.html#inheritance>`_. Closes `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>`_

**Tidyup**:

* Lots of warnings fixed from running prospector on itself

Page 2 of 16

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.