Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Code to remove in parsetok? #49116

Closed
ganderson mannequin opened this issue Jan 7, 2009 · 2 comments
Closed

Code to remove in parsetok? #49116

ganderson mannequin opened this issue Jan 7, 2009 · 2 comments
Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error

Comments

@ganderson
Copy link
Mannequin

ganderson mannequin commented Jan 7, 2009

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']
@ganderson ganderson mannequin added interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error labels Jan 7, 2009
@ganderson
Copy link
Mannequin Author

ganderson mannequin commented Jan 7, 2009

At the lines 99 .. 103, there are the message on Python 2.6.

@amauryfa
Copy link
Member

amauryfa commented Jan 7, 2009 

The code is excluded from compilation with a
    #ifdef PY_PARSER_REQUIRES_FUTURE_KEYWORD

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.

@amauryfa amauryfa closed this as completed Jan 7, 2009
@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs) type-bug An unexpected behavior, bug, or error
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@amauryfa