Any comments? My draft of a new PEP.

Gerhard Häring gerhard.nospam at
Tue Aug 14 21:54:48 CEST 2001

Something similar was proposed a few months ago. I've put it now into PEP-form.
This is only a rough draft. What do you think of it?

If a few more people than just me think that this is a good idea I'll try to
submit this as a PEP.



PEP: <pep-no.>
Title: Reserving Keywords For Possible Future Use
Version: Python 2.2
Author: gerhard at (Gerhard Haering)
Status: Draft of Draft
Type: Standards track
Created: 14-Aug-2001
Post-History: <none>

    To avoid long transition periods when a new Python feature requires a new
    keyword, this PEP proposes to reserve a set of keywords "in advance".

    These are the list of keywords reserved for possible future use:

    abstract, directive, foreign, interface, static, yield

    In Python 2.2, a warning will be emitted as soon as any of the above is
    used as an identifier, for example:

    Warning: 'yield' will become a reserved keyword in the future

    In Python 2.3, all of the above become reserved keywords, and using them as
    identifiers will generate a Syntax error.  

    If a new Python feature requires the introduction of a new keywords in the
    future and the keyword was in the set of keywords reserved for possible
    future use, the new feature can be made available immediately. There will
    be no need to make a "from __future import" statement during for one Python
    version iteration, like with the introduction of simple generators in
    Python 2.2.        

Open Issues
    Which keywords to reserve.


    This document has been placed in the public domain.

Local Variables:
mode: indented-text
indent-tabs-mode: nil

mail:   gerhard <at> bigfoot <dot> de       registered Linux user #64239
web:    public key at homepage
public key fingerprint: DEC1 1D02 5743 1159 CD20  A4B6 7B22 6575 86AB 43C0
reduce(lambda x,y:x+y,map(lambda x:chr(ord(x)^42),tuple('zS^BED\nX_FOY\x0b')))

More information about the Python-list mailing list