Repository navigation
null source chars handled oddly by tokenize #41466
Description
| BPO | 1105770 |
|---|---|
| Nosy | @gvanrossum, @devdanzin |
| Files |
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 2021-06-17.15:19:21.992>
created_at = <Date 2005-01-20.07:35:04.000>
labels = ['interpreter-core', 'type-bug']
title = 'null source chars handled oddly by tokenize'
updated_at = <Date 2021-06-17.15:19:21.990>
user = 'https://bugs.python.org/rcharney'bugs.python.org fields:
activity = <Date 2021-06-17.15:19:21.990>
actor = 'gvanrossum'
assignee = 'none'
closed = True
closed_date = <Date 2021-06-17.15:19:21.992>
closer = 'gvanrossum'
components = ['Interpreter Core']
creation = <Date 2005-01-20.07:35:04.000>
creator = 'rcharney'
dependencies = []
files = ['1562']
hgrepos = []
issue_num = 1105770
keywords = []
message_count = 4.0
messages = ['24004', '24005', '82112', '396005']
nosy_count = 4.0
nosy_names = ['gvanrossum', 'rcharney', 'ajaksu2', 'Alexandre.Zani']
pr_nums = []
priority = 'normal'
resolution = 'duplicate'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue1105770'
versions = ['Python 3.1', 'Python 2.7', 'Python 3.2']
Activity
rcharney commentedon Jan 20, 2005
When null characters appear in the source, outside
literals, tokenize seems to either: skip the null
character and the next two following characters; or
ignore the remainder of the line, including the newline
character.
(To see the invalid characters, use vim, or an editor
that displays control characters when needed.)
birkenfeld commentedon Jan 10, 2006
Logged In: YES
user_id=1188172
Confirmed with current SVN heads.
devdanzin commentedon Feb 14, 2009
Confirmed on trunk at rev69546.
[-]null source chars handled oddly[/-][+]null source chars handled oddly by tokenize[/+]gvanrossum commentedon Jun 17, 2021
Closing in favor of bpo-20115.