Keep consistent line endings

[radoering]

Resolves: #200

With this change, when reading a toml file with consistent line endings, changing the content and writing the content into a file, the result is a file with the same consistent line endings as the input file.

Further, default line endings for Windows when creating a new toml file will be Windows line endings ("\r\n") again.

This change is not perfect, because it only ensures that the written file has consistent line endings. Dumping the changed TomlDocument as string still has inconsistent line endings. However, keeping consistent line endings for TomlDocument seems to require way more effort since hard coded "\n" is used in many places.

[frostming]

Hmm, that does break the integration tests, please have a look? @radoering

[radoering]

@frostming poetry tests were kind of unintentionally expecting inconsistent line endings... They should be forward compatible now. Please re-run the failing tests.

[frostming]

LGTM

[bmitc]

Further, default line endings for Windows when creating a new toml file will be Windows line endings ("\r\n") again.

Is it possible to add a configuration setting for this? I am using Poetry, and it is rather tedious that Poetry automatically generates files using CRLF line endings when I'm on Windows when everything else in my editor creates files with LF line endings, on any operating system. I configure VS Code and Git such that only LF files are created and Git never changes them.

[frostming]

Is it possible to add a configuration setting for this?

You are free not to use the TOMLFile API and read and tomlkit.parse the document yourself.