[Python-Dev] Order of Fixers

[Thomas Wouters]

On Wed, Mar 19, 2008 at 11:01 AM, David Wolever <wolever at cs.toronto.edu>
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 __future__ import ...' statement.
>
> I'm tempted to simply change fix_future to fix_zz_future... But that
> has some obvious drawbacks.
> Alternately, if future is the only dependent module, it might be
> marginally cleaner to simply special-case it in
> refactor.get_all_fix_names.
>
> So, any better suggestions?
>

I would fix the from-future fixer to not remove futures that are specific to
3.0, and let the fixers specific to those features remove them.

-- 
Thomas Wouters <thomas at python.org>

Hi! I'm a .signature virus! copy me into your .signature file to help me
spread!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20080319/afab0e67/attachment.htm