Repository navigation
Code to remove in parsetok? #49116
Description
| BPO | 4866 |
|---|---|
| Nosy | @amauryfa |
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 = None
closed_at = <Date 2009-01-07.14:37:22.208>
created_at = <Date 2009-01-07.14:04:40.853>
labels = ['interpreter-core', 'type-bug', 'invalid']
title = 'Code to remove in parsetok?'
updated_at = <Date 2009-01-07.14:37:22.175>
user = 'https://bugs.python.org/ganderson'bugs.python.org fields:
activity = <Date 2009-01-07.14:37:22.175>
actor = 'amaury.forgeotdarc'
assignee = 'none'
closed = True
closed_date = <Date 2009-01-07.14:37:22.208>
closer = 'amaury.forgeotdarc'
components = ['Interpreter Core']
creation = <Date 2009-01-07.14:04:40.853>
creator = 'ganderson'
dependencies = []
files = []
hgrepos = []
issue_num = 4866
keywords = []
message_count = 2.0
messages = ['79332', '79333']
nosy_count = 2.0
nosy_names = ['amaury.forgeotdarc', 'ganderson']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue4866'
versions = ['Python 3.0']
Activity
ganderson commentedon Jan 7, 2009
At the lines 99 .. 103, there are the message on Python 2.6.
amauryfa commentedon Jan 7, 2009
There is no __future__ feature in 3.0 for the moment, but the code stays
here as a placeholder, to remind developers what they need to do to
support __future__ flags that change the behavior of the lexer.