lp:pyflakes
This page might be outdated: it depends on the Launchpad import machines, and import runs approximately every 8 hours
https:/
The master repository is now at GitHub:
https:/
- Get this branch:
- bzr branch lp:pyflakes
Branch merges
Branch information
Import details
This branch is an import of the HEAD branch of the Git repository at git://github.com/pyflakes/pyflakes.git.
Last successful import was on 2016-05-04.
Recent revisions
- 209. By Ćukasz Langa on 2016-04-12
-
Warn against reusing exception names after the except: block on Python 3
- 208. By John Vandenberg on 2016-03-15
-
Importation classes with imported name and alias
In order to solve many corner cases related to imports,
more information is needed about each import.This change creates two new classes:
- SubmoduleImportation
- ImportationFromAnd adds an optional parameter full_name to the super class
Importation.Functionally, this change only improves existing error messages
to report the full imported name where previously an error
would include only the import alias. - 206. By Ian Cordasco <email address hidden> on 2016-01-25
-
Merge pull request #58 from jayvdb/
api_main_ args Allow passing args to main()
- 205. By Steven Myint <email address hidden> on 2015-12-22
-
Merge pull request #56 from pyflakes/matmul
Handle matrix-
multiplication operator ("@") - 204. By John Vandenberg on 2015-11-24
-
Check feature names imported from future
As '*' does not appear in __future_
_.all_feature_ names, this
also reports an error on : from __future__ import * - 203. By John Vandenberg on 2015-11-24
-
Allow __future__ in doctest
Replaces plain attribute Checker.
futuresAllowed with a property
that supports __future__ in both module and doctest. - 202. By John Vandenberg on 2015-11-24
-
Process doctest scope directly under the module scope
Explicitly place the doctest directly under the module scope,
instead of processing it while within the scope where the
docstring was encountered.
Also do not process doctest which are not processed by default
according to the doctest documentation.The primary benefit of moving the doctest scope directly under
the module scope is that it may be efficiently identified,
as it may only appear second in the stack.However it also ensures that the doctest scope can not access
names in scopes between the module scope and the object where the
docstring was encountered. As it was, class scope rules prevented
the doctest scope from accessing names in a class scope, however
the doctest scope was able to access names in an outer function,
if the doctest appeared in a nested function.
Note that there was no real bug there, as the doctest module does
not process doctest in nested functions (Python issue #1650090),
so doctest appearing in nested functions are informational only.
pyflakes previously inspected doctest in nested functions,
and now these are ignored. - 201. By John Vandenberg on 2015-11-24
-
Report each usage of star imports
Also detect unused star imports.
- 200. By John Vandenberg on 2015-11-24
-
Merge pull request #51 from jayvdb/assert-tuple
Report assert using tuple
Branch metadata
- Branch format:
- Branch format 7
- Repository format:
- Bazaar repository format 2a (needs bzr 1.16 or later)