Passive checker of Python programs

Edit Package python-pyflakes
http://www.divmod.org/trac/wiki/DivmodPyflakes

Pyflakes is program to analyze Python programs and detect 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.

Author:
--------
Moe Aboulkheir

Refresh
Refresh
Source Files
Filename Size Changed
pyflakes-2.2.0.tar.gz 0000065307 63.8 KB
python-pyflakes.changes 0000012721 12.4 KB
python-pyflakes.spec 0000002208 2.16 KB
Revision 25 (latest revision is 38)
Yuchen Lin's avatar Yuchen Lin (maxlin_factory) accepted request 805797 from Benjamin Greiner's avatar Benjamin Greiner (bnavigator) (revision 25)
- specfile:
  * update copyright year
- update to version 2.2.0:
  * Include column information in error messages
  * Fix @overload detection with other decorators and in non-global
    scopes
  * Fix return-type annotation being a class member
  * Fix assignment to _ in doctests with existing _ name
  * Namespace attributes which are attached to ast nodes with
    _pyflakes_ to avoid conflicts with other libraries (notably
    bandit)
  * Add check for f-strings without placeholders
  * Add check for unused/extra/invalid 'string literal'.format(...)
  * Add check for unused/extra/invalid 'string literal % ...
  * Improve python shebang detection
  * Allow type ignore to be followed by a code # type:
    ignore[attr-defined]
  * Add support for assignment expressions (PEP 572)
  * Support @overload detection from typing_extensions as well
  * Fix @overload detection for async functions
  * Allow continue inside finally in python 3.8+
  * Fix handling of annotations in positional-only arguments
  * Make pyflakes more resistant to future syntax additions
  * Fix false positives in partially quoted type annotations
  * Warn about is comparison to tuples
  * Fix Checker usage with async function subtrees
  * Add check for if of non-empty tuple
  * Switch from optparse to argparse
  * Fix false positives in partially quoted type annotations in
    unusual contexts
  * Be more cautious when identifying Literal type expressions
Comments 0
openSUSE Build Service is sponsored by