python 3's adoption

Paul Rubin no.email at nospam.invalid
Wed Jan 27 08:37:00 CET 2010


Steven D'Aprano <steven at REMOVE.THIS.cybersource.com.au> writes:
> Sorry, I meant consistent with the rest of Python, which mostly uses 
> functions/methods and only rarely statements (e.g. del and import).

yield, assert, if/else, return, etc.  If we're after that kind of
consistency, why not get rid of all those statements too?  They have
already partly done it with yield, and they ended up introducing a new
separate if/else expression syntax as an alternative to the statement.

> I don't pretend that the transition between statement and function syntax 
> will be anything but inconvenient, but I believe the end result will be 
> worth it.

This just seems like a gratuitous change with very little benefit.  
Changing a bunch of list functions to instead return iterators is
a much deeper change that will cause larger amounts of breakage, but
it has quite a lot of benefits, so there's a stronger case for it.



More information about the Python-list mailing list