Repository navigation
io.py problems on Windows #45382
Description
| BPO | 1041 |
|---|---|
| Nosy | @gvanrossum, @theller |
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-08-29.20:48:05.583>
created_at = <Date 2007-08-28.06:09:59.036>
labels = ['OS-windows']
title = 'io.py problems on Windows'
updated_at = <Date 2007-08-29.20:48:05.581>
user = 'https://github.com/theller'bugs.python.org fields:
activity = <Date 2007-08-29.20:48:05.581>
actor = 'gvanrossum'
assignee = 'none'
closed = True
closed_date = <Date 2007-08-29.20:48:05.583>
closer = 'gvanrossum'
components = ['Windows']
creation = <Date 2007-08-28.06:09:59.036>
creator = 'theller'
dependencies = []
files = []
hgrepos = []
issue_num = 1041
keywords = []
message_count = 2.0
messages = ['55353', '55440']
nosy_count = 2.0
nosy_names = ['gvanrossum', 'theller']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1041'
versions = ['Python 3.0']
Activity
theller commentedon Aug 28, 2007
Running the PCBuild\rt.bat script fails when it compares the expected output
with the actual output. Some inspection shows that the comparison fails
because
there are '\n' linefeeds in the expected and '\n\r' linefeeds in the
actual output:
c:\svn\py3k\PCbuild>python_d -E -tt ../lib/test/regrtest.py
test_grammar
test test_grammar produced unexpected output:
*** mismatch between line 1 of expected output and line 1 of actual
output:
+ test_grammar
? +
(['test_grammar\n'], ['test_grammar\r\n'])
... and so on ...
(The last line is printed by some code I added to Lib\regrtest.py.)
It seems that this behaviour was introduced by r57186:
New I/O code from Tony Lownds implement newline feature correctly,
and implements .newlines attribute in a 2.x-compatible fashion.
The patch at http://bugs.python.org/issue1029 apparently fixes this problem.
gvanrossum commentedon Aug 29, 2007
I'm guessing this is fixed now that that patch is submitted.