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.

Author loewis
Recipients benjamin.peterson, loewis
Date 2008-11-26.06:45:26
SpamBayes Score 0.0033632088
Marked as misclassified No
Message-id <492CF084.4090707@v.loewis.de>
In-reply-to <1afaf6160811251526r6ce4b9c8n4a25f6d0a2d1d81b@mail.gmail.com>
Content
> This is true of many fixers. What is the use case?

In this case, I wanted to work around the fixer working incorrectly
for commands, but still have it continue to work for all the other
modules it fixes. The context is the setup.py script of Django.

> Is that reasonable also?

Sure! People will accept that they have to reorganize the source
before 2to3 can work correctly. More precisely, if they follow the
"convert once, cut the bridges" approach, they can just manually
unfix the few places that 2to3 got wrong. If they follow the
"single source" approach, they will accept that they have to
reformulate.
History
Date User Action Args
2008-11-26 06:45:31loewissetrecipients: + loewis, benjamin.peterson
2008-11-26 06:45:29loewislinkissue4423 messages
2008-11-26 06:45:28loewiscreate