[ python-Bugs-1105770 ] null source chars handled oddly

SourceForge.net noreply at sourceforge.net
Wed Jan 11 00:08:37 CET 2006


Bugs item #1105770, was opened at 2005-01-20 08:35
Message generated for change (Settings changed) made by birkenfeld
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1105770&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Parser/Compiler
Group: None
>Status: Open
Resolution: None
Priority: 5
Submitted By: Reginald B. Charney (rcharney)
Assigned to: Nobody/Anonymous (nobody)
Summary: null source chars handled oddly

Initial Comment:
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.)

----------------------------------------------------------------------

Comment By: Georg Brandl (birkenfeld)
Date: 2006-01-11 00:07

Message:
Logged In: YES 
user_id=1188172

Confirmed with current SVN heads.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1105770&group_id=5470


More information about the Python-bugs-list mailing list