Showing content from http://mail.python.org/pipermail/python-dev/attachments/20080319/afab0e67/attachment.htm below:
<br><br><div class="gmail_quote">On Wed, Mar 19, 2008 at 11:01 AM, 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?<br>
</blockquote><div><br>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.<br></div></div><br>-- <br>Thomas Wouters <<a href="mailto:thomas@python.org">thomas@python.org</a>><br>
<br>Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4