Thanks for the comments.

Re: "stuff", if you look at other parts of the code, that is how the triple is referred to -- fyi on how the name "stuff" came to be :) I was also at a loss for a better name, and went with the contextual references.

Re: using 2to3 -- Brett, in many cases I actually tried to come up with a consistent name. IIRC 2to3 will put in XXX_fixme_123 or something like that. Or it did when I last tried. Anyway, if you end up using 2to3, I would really appreciate it if you also picked up the inspect.py docstring change.

Re: signature changes (eg LeftShift) and repr (FloorDiv) -- that is generated code, and that is why "repr" is used. I chose to change the generation source rather than the generation machinery as I was changing the source anyway, to account for the changes to parameter syntax. That is why there are API changes. Given that other API changes were made and those class constructors are more or less an internal API (created through compiler.parse),
I believe this is the best way of dealing with the changes.

Brett, If you need me to remove the 2to3 doc toolchain patches, I can do that.