This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Misspelling in future.c in 2.5.1 source (handl should be handle)
Type: Stage:
Components: Interpreter Core Versions: Python 2.6, Python 2.5
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: brad, georg.brandl
Priority: low Keywords:

Created on 2008-01-07 14:08 by brad, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg59445 - (view) Author: Brad Tilley (brad) Date: 2008-01-07 14:08
/* A subsequent pass will detect future imports that don't
	   appear at the beginning of the file.  There's one case,
	   however, that is easier to handl here: A series of imports
	   joined by semi-colons, where the first import is a future
	   statement but some subsequent import has the future form
	   but is preceded by a regular import.
	*/
msg59463 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2008-01-07 16:42
Fixed in r59820.
History
Date User Action Args
2022-04-11 14:56:29adminsetgithub: 46095
2008-01-07 16:42:10georg.brandlsetstatus: open -> closed
resolution: accepted -> fixed
messages: + msg59463
nosy: + georg.brandl
2008-01-07 14:41:58christian.heimessetpriority: low
resolution: accepted
components: + Interpreter Core, - None
versions: + Python 2.6
2008-01-07 14:08:29bradcreate