Repository navigation
2to3 crashes on input files with no trailing newlines #45342
Description
| BPO | 1001 |
|---|
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 2007-09-06.18:26:37.469>
created_at = <Date 2007-08-23.19:54:02.393>
labels = ['expert-2to3', 'type-crash']
title = '2to3 crashes on input files with no trailing newlines'
updated_at = <Date 2008-01-06.22:29:45.680>
user = 'https://bugs.python.org/adrianholovaty'bugs.python.org fields:
activity = <Date 2008-01-06.22:29:45.680>
actor = 'admin'
assignee = 'collinwinter'
closed = True
closed_date = <Date 2007-09-06.18:26:37.469>
closer = 'collinwinter'
components = ['2to3 (2.x to 3.x conversion tool)']
creation = <Date 2007-08-23.19:54:02.393>
creator = 'adrianholovaty'
dependencies = []
files = []
hgrepos = []
issue_num = 1001
keywords = []
message_count = 4.0
messages = ['55195', '55197', '55710', '55711']
nosy_count = 2.0
nosy_names = ['collinwinter', 'adrianholovaty']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue1001'
versions = ['Python 3.0']
Activity
adrianholovaty commentedon Aug 23, 2007
The 2to3 Python 3k migration utility crashes with the following
traceback on any input file that does *not* have a trailing newline. It
doesn't seem to matter whether the input file needs modifications or not.
RefactoringTool: Can't parse /path/to/testing2.py: ParseError: bad
input: type=0, value='', context=('\n', (2, 0))
RefactoringTool: No files need to be modified.
RefactoringTool: There was 1 error:
RefactoringTool: Can't parse /path/to/testing2.py: ParseError: bad
input: type=0, value='', context=('\n', (2, 0))
adrianholovaty commentedon Aug 23, 2007
(Sorry, the previous error snippet isn't a traceback as I had said. It's
the error text.)
collinwinter commentedon Sep 6, 2007
I believe this was fixed in r57942; can you test to see if you still
have this problem?
adrianholovaty commentedon Sep 6, 2007
I just checked, and, yes, it's been fixed.