On Wed, Mar 19, 2008 at 11:01 AM, David Wolever <[EMAIL PROTECTED]>
wrote:
> At the moment, fixers are run in alphabetical order -- but this poses
> a problem, because some depend on others (for example, fix_print will
> need to be run _before_ fix_future, because fix_print looks for the
> 'from _
On 19-Mar-08, at 2:18 PM, Benjamin Peterson wrote:
So, any better suggestions?
I would create a list of fixers that need to go first in
refactor.py and run those in order. If you wanted to get complex,
you could add a requires member to fixes, but that is probably
overkill.
Ok, so I was dig
On Wed, Mar 19, 2008 at 1:01 PM, David Wolever <[EMAIL PROTECTED]>
wrote:
> At the moment, fixers are run in alphabetical order -- but this poses
> a problem, because some depend on others (for example, fix_print will
> need to be run _before_ fix_future, because fix_print looks for the
> 'from __
At the moment, fixers are run in alphabetical order -- but this poses
a problem, because some depend on others (for example, fix_print will
need to be run _before_ fix_future, because fix_print looks for the
'from __future__ import ...' statement.
I'm tempted to simply change fix_future to f
