<br><br><div class="gmail_quote">On Wed, Mar 19, 2008 at 1:01 PM, David Wolever <<a href="mailto:wolever@cs.toronto.edu">wolever@cs.toronto.edu</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
At the moment, fixers are run in alphabetical order -- but this poses<br>
a problem, because some depend on others (for example, fix_print will<br>
need to be run _before_ fix_future, because fix_print looks for the<br>
'from __future__ import ...' statement.<br>
<br>
I'm tempted to simply change fix_future to fix_zz_future... But that<br>
has some obvious drawbacks.<br>
Alternately, if future is the only dependent module, it might be<br>
marginally cleaner to simply special-case it in<br>
refactor.get_all_fix_names.<br>
<br>
So, any better suggestions?</blockquote><div>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.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org">Python-Dev@python.org</a><br>
<a href="http://mail.python.org/mailman/listinfo/python-dev" target="_blank">http://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="http://mail.python.org/mailman/options/python-dev/musiccomposition%40gmail.com" target="_blank">http://mail.python.org/mailman/options/python-dev/musiccomposition%40gmail.com</a><br>
</blockquote></div><br>