RetroSearch Browse

Wed Mar 19 19:18:59 CET 2008 · https://mail.python.org/pipermail/python-dev/2008-March/077840.html

On Wed, Mar 19, 2008 at 1:01 PM, 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 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.

>
>
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> http://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> http://mail.python.org/mailman/options/python-dev/musiccomposition%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20080319/6427d102/attachment.htm 

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-March/077840.html below:

[Python-Dev] Order of Fixers