[Python-3000] PEP 3113 transition plan

Ka-Ping Yee python-dev at zesty.ca
Wed Mar 7 03:20:10 CET 2007

On Tue, 6 Mar 2007, Collin Winter wrote:
> I'd like to strike the part about making "x.next()" ->
> "next(x)"/"x.__next__()" determined by the presence of a module-level
> "next" binding. I'd rather see the transformation always be "x.next()"
> -> "next(x)" and warn on top-level "next"s. Doing it the way the PEP
> suggests is possible, but ugly (requires an unusually-complicated
> fixer) and slow. I can give you warnings on the following items,
> though:
> - global assignments to "next".
> - global definitions of a "next" function.
> - global imports of anything named "next".
> - assignments to "__builtin__.next".

That sounds pretty good to me.  I've updated the PEP.  (In "global
assignments" don't forget bindings introduced by "for next in blah".)

-- ?!ng

More information about the Python-3000 mailing list