[issue1755] Misspelling in future.c in 2.5.1 source (handl should be handle)

Georg Brandl added the comment: Fixed in r59820. -- nosy: +georg.brandl resolution: accepted -> fixed status: open -> closed __ Tracker <[EMAIL PROTECTED]> __ _

[issue1755] Misspelling in future.c in 2.5.1 source (handl should be handle)

Changes by Christian Heimes: -- components: +Interpreter Core -None priority: -> low resolution: -> accepted versions: +Python 2.6 __ Tracker <[EMAIL PROTECTED]> __ _

[issue1755] Misspelling in future.c in 2.5.1 source (handl should be handle)

New submission from Brad Tilley: /* 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