Created by Florent on 2013-01-24 and last modified on 2016-04-12

This page might be outdated: it depends on the Launchpad import machines, and import runs approximately every 8 hours

The master repository is now at GitHub:

Get this branch:
bzr branch lp:pyflakes

Branch merges

Related bugs

Related blueprints

Branch information

Pyflakes Dev

Import details

Import Status: Failed

This branch is an import of the HEAD branch of the Git repository at git://github.com/pyflakes/pyflakes.git.

The import has been suspended because it failed 5 or more times in succession.

Last successful import was on 2016-05-04.

Import started on 2016-07-21 on pear and finished on 2016-07-21 taking 15 seconds — see the log
Import started on 2016-05-08 on pear and finished on 2016-05-08 taking 15 seconds — see the log
Import started on 2016-05-06 on neumayer and finished on 2016-05-06 taking 25 seconds — see the log
Import started on 2016-05-05 on russkaya and finished on 2016-05-05 taking 30 seconds — see the log

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
- ImportationFrom

And adds an optional parameter full_name to the super class

Functionally, this change only improves existing error messages
to report the full imported name where previously an error
would include only the import alias.

207. By Phil Frost on 2016-03-01

Increment version to 1.1.0

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)
This branch contains Public information 
Everyone can see this information.