classification
Title: izip fixer generates incorrect import statement
Type: Stage:
Components: 2to3 (2.x to 3.x conversion tool) Versions:
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: wolever Nosy List: loewis, wolever
Priority: normal Keywords:

Created on 2008-03-23 20:39 by loewis, last changed 2008-03-24 00:32 by wolever. This issue is now closed.

Messages (2)
msg64375 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2008-03-23 20:39
Currently (r61811), the code

from itertools import izip

gets fixed to

from itertools import

This is incorrect; the import statement should be removed altogether.
msg64386 - (view) Author: David Wolever (wolever) * (Python committer) Date: 2008-03-24 00:30
Ah, nuts -- I had a test case for this, but it was testing with 'from  
itertools import izip, imap'... But not the single node >_<
It has been fixed, and appropriate test has been added, in r61824.

On 23-Mar-08, at 4:39 PM, Martin v. Löwis wrote:

>
> New submission from Martin v. Löwis <martin@v.loewis.de>:
>
> Currently (r61811), the code
>
> from itertools import izip
>
> gets fixed to
>
> from itertools import
>
> This is incorrect; the import statement should be removed altogether.
>
> ----------
> assignee: David Wolever
> components: 2to3 (2.x to 3.0 conversion tool)
> messages: 64375
> nosy: David Wolever, loewis
> severity: normal
> status: open
> title: izip fixer generates incorrect import statement
>
> __________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue2468>
> __________________________________
History
Date User Action Args
2008-03-24 00:32:45woleversetstatus: open -> closed
resolution: fixed
2008-03-24 00:30:58woleversetmessages: + msg64386
2008-03-23 20:39:01loewiscreate