➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jim.Jewett
Recipients Jim.Jewett, docs@python
Date 2012-01-19.00:45:56
SpamBayes Score 5.9363352e-05
Marked as misclassified No
Message-id <1326933957.4.0.830452813069.issue13820@psf.upfronthosting.co.za>
In-reply-to
Content 
http://docs.python.org/reference/lexical_analysis.html

Changed in version 2.5: Both as and with are only recognized when the with_statement future feature has been enabled. It will always be enabled in Python 2.6. See section The with statement for details. Note that using as and with as identifiers will always issue a warning, even when the with_statement future directive is not in effect.


That was reasonable wording for 2.5 itself, but at this point, I think it would be simpler to add a Changed in version 2.6 entry.  Perhaps:

Changed in version 2.5: Using as or with as identifiers triggers a warning.  Using them as statements requires the with_statement future feature.
Changed in Python 2.6: as and with became full keywords.
History
Date User Action Args
2012-01-19 00:45:57Jim.Jewettsetrecipients: + Jim.Jewett, docs@python
2012-01-19 00:45:57Jim.Jewettsetmessageid: <1326933957.4.0.830452813069.issue13820@psf.upfronthosting.co.za>
2012-01-19 00:45:56Jim.Jewettlinkissue13820 messages
2012-01-19 00:45:56Jim.Jewettcreate