[Python-3000] PEP: rename it.next() to it.__next__(), add a next() built-in

[Barry Warsaw]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 5, 2007, at 5:16 PM, Greg Ewing wrote:

> Also I'm not sure I like this idea. It smells like
> an abuse of the notion of calling to me. One doesn't
> normally expect that calling a callable object has
> a side effect on the callable itself.

Perhaps, but I think there's a valid use case for calling "next"  
explicitly, and I would really hate for that to be spelled  
"it.__next__()".

- -Barry

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iQCVAwUBReyY+XEjvBPtnXfVAQLdmgP9EAJzYtvuXHFJ1DoWj42QOT79xCqpxNMs
qcLDF9sRCprrzMWHrjlUcC0NZmBJGXotB4TNMO2CtkwbidiIBweo0xwdgwaUDCED
gV+tzrtQtIx516Lv/7gfR08yDl3TmkckVOmaQrQ2RT6QiRuT59+IkhIG9yKlbezn
oo+dODRTYRQ=
=6eYL
-----END PGP SIGNATURE-----