Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configs write in binary mode AND are encoded in the event of unicode #39

Merged
merged 4 commits into from
Mar 11, 2014

Conversation

robdennis
Copy link
Member

After pulling in MichaelHipps proposed changes, I worked to get the unit tests passing on *nix at least, and that necessitated an additional change to how we write things out (need to encode the string that we're writing to file)

MichaelHipp and others added 4 commits March 1, 2014 10:47
On win32 when the filename is given at instantiation time it was saving the files with \r\r\n at eol. If 'newlines' was set to '\n' it was saving files with \r\n. Changing file open to binary fixes this so the write() doesn't redo the line endings.
The doc said it uses os.sep, but it should read os.linesep for default for newlines
…writing out in binary mode; handling encoding that in a py2/3-compatible way
robdennis added a commit that referenced this pull request Mar 11, 2014
configs write in binary mode AND are encoded in the event of unicode
@robdennis robdennis merged commit 6e5c39f into DiffSK:master Mar 11, 2014
@robdennis robdennis added this to the 5.0.3 - next bug fix release milestone Mar 20, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants