On 19-Mar-08, at 2:18 PM, Benjamin Peterson wrote:
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.
Ok, so I was digging around a bit and there is the option to traverse
the tree in preorder or postorder. While the actual order does not
matter in this case, what does matter is that the preorder fixers are
run first -- so I've just dropped the print fixer in there (and
commented everything).
This isn't a great general solution... But, at the moment, there is
no need for it to be. If the need for a general solution arises,
that can be added :)_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
