On Sun, Dec 14, 2008 at 20:02, Lennart Regebro wrote:
> On Sun, Dec 14, 2008 at 19:49, Alexandre Vassalotti
> wrote:
>>> 3.0, I haven't tried with trunk yet, and possibly it's a more
>>> complicated usecase.
>>
>> Strange, fix_imports in Python 3.0 (final) looks fine. If you can come
>> up with a
On Sun, Dec 14, 2008 at 19:49, Alexandre Vassalotti
wrote:
>> 3.0, I haven't tried with trunk yet, and possibly it's a more
>> complicated usecase.
>
> Strange, fix_imports in Python 3.0 (final) looks fine. If you can come
> up with a reproducible example, please open a bug on bugs.python.org
> an
On Sun, Dec 14, 2008 at 1:34 PM, Lennart Regebro wrote:
> On Sun, Dec 14, 2008 at 19:19, Alexandre Vassalotti
> wrote:
>> Which revision of python are you using? I tried the test-case you gave
>> and 2to3 translated it perfectly.
>
> 3.0, I haven't tried with trunk yet, and possibly it's a more
>
On Sun, Dec 14, 2008 at 19:19, Alexandre Vassalotti
wrote:
> Which revision of python are you using? I tried the test-case you gave
> and 2to3 translated it perfectly.
3.0, I haven't tried with trunk yet, and possibly it's a more
complicated usecase.
--
Lennart Regebro: Zope and Plone consulting
On Fri, Dec 12, 2008 at 11:39 AM, Lennart Regebro wrote:
> The fix_imports fix seems to fix only the first import per line that you have.
> So if you do for example
> import urllib2, cStringIO
> it will not fix cStringIO.
>
> Is this a bug or a feature? :-) If it's a feature it should warn at
>
Le Friday 12 December 2008 17:39:33 Lennart Regebro, vous avez écrit :
> The fix_imports fix seems to fix only the first import per line that you
> have. So if you do for example
>import urllib2, cStringIO
> it will not fix cStringIO.
>
> Is this a bug or a feature? :-)
I prefer to see that as
