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.9+.
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.15 -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.
Changelog
Please see NEWS.rst.
Release files for pyflakes 4.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyflakes-4.1.0.tar.gz | 67.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyflakes-4.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details |
Total release size: 133.5 kB
Release files / pyflakes-4.1.0.tar.gz
| Download URL | pyflakes-4.1.0.tar.gz |
|---|---|
| Size | 67.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
592beb57058eb82eb190fb7514f2081c555c51000b029ff71286a681e6cf2f83
|
|
BLAKE2b-256 checksum How to use checksums |
9b43f4566b992ab97abd18426aeba516a83c7a833230614a2c3f4d3e9d8ff0f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / pyflakes-4.1.0-py2.py3-none-any.whl
| Download URL | pyflakes-4.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 66.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b2e05e6bac8e49b67be2a6ffa63422c60f7193fc72e8180255907b41ec997dc1
|
|
BLAKE2b-256 checksum How to use checksums |
fd5298c9a0e4718abe887121279457bc7140115df22d714b7183880eb61e359f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for pyflakes 4.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
