Plone.recipe.codeanalysis

Latest version: v3.0.1

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

Scan your dependencies

Page 3 of 5

2.0a1

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

- Added multiprocessing. This will dramatically increase speed on large
packages when using pre-commit hooks.
[saily]

- Return correct exit codes for console-scripts.
Fixes https://github.com/plone/plone.recipe.codeanalysis/issues/66
[saily]

- Refactor whole linters framework to use OO design patterns, inherit from
``Analyser`` abstract base class.
Fixes https://github.com/plone/plone.recipe.codeanalysis/issues/62
[saily]

- Add bootstrap-buildout.py to flake8-exclude default. zc.buildout > 2 uses
bootstrap-buildout.py instead of bootstrap.py.
[timo]

1.1

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

- Add a check to look for hasattr() calls, which are considered bad practice.
[gforcada, jensens]

- Add option to store flake8 output if jenkins is False
[Michael Davis]

- Fix find_files from utils to find files, not directories
[do3cc]

1.0

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

- Nothing changed since 1.0rc1.

1.0rc1

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

- Return a string to avoid TypeError when no file was checked with ``jscs``.
[saily]

- Check import sorting in ``code_analysis_imports`` and add tests for
clean and sorted imports.
[saily]

- Refactor ``code_analysis_clean_lines`` to use a new method to retrieve
files and avoid too complex violation.
[saily]

1.0b8

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

- Add ``clean-lines-exclude`` support and updated README.
[saily]

- Added tests for clean-lines checks.
[saily]

- Use indices for format() to support Python 2.6.
Fixes https://github.com/plone/plone.recipe.codeanalysis/issues/77
[timo]

1.0b7

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

- Add Javascript Code Style Checker ``jscs`` support.
[saily]

- Remove hard dependency on i18ndude and zptlint; this will reduce the number
of Zope/Plone direct dependencies to make life happier to people using
Pyramid and other web Python-based development frameworks.
Fixes https://github.com/plone/plone.recipe.codeanalysis/issues/53
[hvelarde]

- Do not print out jshint and csslint output for Jenkins. Those files can
become quite large.
[timo]

Page 3 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.