You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee='https://github.com/terryjreedy'closed_at=<Date2012-01-21.05:35:57.279>created_at=<Date2012-01-19.00:45:56.824>labels= ['type-feature', 'docs']
title='2.6 is no longer in the future'updated_at=<Date2012-01-21.05:35:57.277>user='https://github.com/JimJJewett'
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.
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: