A RetroSearch Logo

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

Search Query:

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

[Python-Dev] Order of Fixers

[Python-Dev] Order of Fixers [Python-Dev] Order of FixersDavid Wolever wolever at cs.toronto.edu
Wed Mar 19 19:01:47 CET 2008
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?

More information about the Python-Dev mailing list

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