Fix an error about line_terminator

Bug #1634754 reported by jian.song
This bug report is a duplicate of:  Bug #1634755: Fix an error about line_terminator. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Incomplete
Undecided
Unassigned

Bug Description

In Linux /n as a newline, and Windows is /r/n, so I will be the
default value is set to "/n" for line_terminator, in fact, the most intuitive
is solved test_operating_system.TestOperatingSystem.test_key_value_file
_codec problem.

before change:http://paste.openstack.org/show/585902/

We can see from the error message:
b"reference = {'key1': 'value1', 'key2': 'value2', 'key3': 'value3'}"
b"actual = {'key1': 'value1\\nkey2=value2\\nkey3=value3'}"

For this reason I think it's about time to split not the cut with a "/n"

Revision history for this message
jian.song (jiansong) wrote :

The company's network speed... Submit repeat every time out...

Revision history for this message
Amrith Kumar (amrith) wrote :

What is the purpose of this bug?

Is it that:

- your development environment is Windows?
- you wish to deploy Trove on Windows?

To be clear, I don't believe that either of these are (currently) within scope for Trove though the former is a smaller ask than the latter.

Changed in trove:
status: New → Incomplete
Revision history for this message
Amrith Kumar (amrith) wrote :

Please describe the problem you are trying to solve (at a slightly higher level than CR-LF vs LF).

Revision history for this message
jian.song (jiansong) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.