ConfigParser uses wrong newline on Windows

[mrblabla]

BPO	13190
Nosy	@ambv

^{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 = 'https://github.com/ambv'
closed_at = <Date 2012-01-23.17:17:36.653>
created_at = <Date 2011-10-16.17:47:51.791>
labels = ['type-bug', 'library']
title = 'ConfigParser uses wrong newline on Windows'
updated_at = <Date 2012-01-23.17:17:36.652>
user = 'https://bugs.python.org/mrblabla'

bugs.python.org fields:

activity = <Date 2012-01-23.17:17:36.652>
actor = 'lukasz.langa'
assignee = 'lukasz.langa'
closed = True
closed_date = <Date 2012-01-23.17:17:36.653>
closer = 'lukasz.langa'
components = ['Library (Lib)']
creation = <Date 2011-10-16.17:47:51.791>
creator = 'mrblabla'
dependencies = []
files = []
hgrepos = []
issue_num = 13190
keywords = []
message_count = 2.0
messages = ['145632', '151829']
nosy_count = 2.0
nosy_names = ['lukasz.langa', 'mrblabla']
pr_nums = []
priority = 'normal'
resolution = 'works for me'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue13190'
versions = ['Python 3.3']

[mrblabla]

ConfigParser writes data to the config file using hard-coded newline: '\n'.
This newline is not suitable for Windows. Therefore, the config file isn't readable in Notepad.exe.

os.linesep should be used instead.

[ambv]

That is indeed the behaviour. Citing the tutorial: "Python on Windows makes a distinction between text and binary files; the end-of-line characters in text files are automatically altered slightly when data is read or written."

When you're opening the file in binary mode, \n characters are not altered. Opening a file that way specifies programmer intent and I don't think we should force os.linesep in that case.