PEP 308: Pep Update

[A. Lloyd Flanagan]

Sheila King <usenet at thinkspot.net> wrote in message news:<b3jgg4.gs.1 at kserver.org>...
> On Thu, 27 Feb 2003 00:06:21 -0600, "Norman Petry" <npetry1 at canada.com>
> wrote in comp.lang.python in article
> <pan.2003.02.27.06.06.21.230621 at canada.com>:
> 
> > 3) reuses existing keywords (if, else) unlike similar proposals like 'x
> > when C else y' which convey precisely the same meaning in a verbose and
> > non-backwards-compatible way.  Adding an entirely new reserved word solely
> > for the benefit (?) of a rarely-used construct seems like an especially
> > bad idea.

Actually, I like 'x when C else y'.  I don't see introducing a keyword
for a new construct as too serious a problem.  Also, I expect the
construct to be used more often than many people seem to expect. 
OTOH, I don't have a serious problem with 'x if C else y'.  So count
me as +1.01 to 'when', +1 to 'if'.

Of course, the way this discussion is going, by the time it's done,
we'll be speaking Arcturan, and it will look something like 'x j^tar C
bdor y'.  :)