python-pyflakes
Port variant v11
Summary Passive checker of Python programs (3.11)
BROKEN
Package version 3.2.0
Homepage https://github.com/PyCQA/pyflakes
Keywords python
Maintainer Python Automaton
License Not yet specified
Other variants v12
Ravenports Buildsheet | History
Ravensource Port Directory | History
Last modified 06 JAN 2024, 17:04:35 UTC
Port created 15 AUG 2018, 15:32:35 UTC
Subpackage Descriptions
single ======== Pyflakes ======== A simple program which checks Python source files for errors. Pyflakes analyzes programs and detects various errors. It works by parsing the source file, not importing it, so it is safe to use on modules with side effects. It's also much faster. It is [available on PyPI] and it supports all active versions of Python: 3.6+. Installation ------------ It can be installed with:: $ pip install --upgrade pyflakes Useful tips: * Be sure to install it for a version of Python which is compatible with your codebase: ``python#.# -m pip install pyflakes`` (for example, ``python3.10 -m pip install pyflakes``) * You can also invoke Pyflakes with ``python#.# -m pyflakes .`` if you want to run it for a specific python version. * If you require more options and more flexibility, you could give a look to Flake8_ too. Design Principles ----------------- Pyflakes makes a simple promise: it will never complain about style, and it will try very, very hard to never emit false positives. Pyflakes is also faster than Pylint_. This is largely because Pyflakes only examines the syntax tree of each file individually. As a consequence, Pyflakes is more limited in the types of things it can check. If you like Pyflakes but also want stylistic checks, you want flake8_, which combines Pyflakes with style checks against `PEP 8`_ and adds per-project configuration ability. Mailing-list ------------ Share your feedback and ideas: `subscribe to the mailing-list `_ Contributing ------------ Issues are tracked on [GitHub]. Patches may be submitted via a `GitHub pull request`_. If you are comfortable doing so, please `rebase your changes`_ so they may be applied to main with a fast-forward merge, and each commit is a coherent unit of work with a well-written log message. If you are not comfortable with this rebase workflow, the project maintainers will be happy to rebase your commits for you. All changes should include tests and pass flake8_. :alt: GitHub Actions build status .. _Pylint: https://pylint.pycqa.org/ .. _flake8: https://pypi.org/project/flake8/ .. _`PEP 8`: https://www.python.org/dev/peps/pep-0008/ .. _`rebase your changes`: https://git-scm.com/book/en/v2/Git-Branching-Rebasing .. _`GitHub pull request`: https://github.com/PyCQA/pyflakes/pulls Changelog --------- Please see `NEWS.rst `_.
Configuration Switches (platform-specific settings discarded)
PY311 ON Build using Python 3.11 PY312 OFF Build using Python 3.12
Package Dependencies by Type
Build (only) python-pip:single:v11
autoselect-python:single:std
Build and Runtime python311:single:std
Download groups
main mirror://PYPIWHL/d4/d7/f1b7db88d8e4417c5d47adad627a93547f44bdc9028372dbd2313f34a855
Distribution File Information
84b5be138a2dfbb40689ca07e2152deb896a65c3a3e24c251c5c62489568074a 62725 pyflakes-3.2.0-py2.py3-none-any.whl
Ports that require python-pyflakes:v11
python-flake8:v11 Source code checker wrapper (3.11)