The new pathlib.Path [read|write]_[binary|text] methods will be very useful, one thing I miss badly is the newline argument for write_text. In some cases text files need a specific line ending (independent from the platform the code is being executed on.) In my mind this is analogous to passing an explicit encoding argument. Of course, one can always use built-in open for this scenario. It would be a nice addition anyway :)

It seems a similar API was suggested in the initial stages at https://bugs.python.org/issue20218#msg209017 . But looking at the reference library in the comment https://github.com/jaraco/path.py I think it's more about converting newlines in the given text with respect to the platform instead of adding one at the end. Thanks

For the newline parameter, what is the expected behaviour? To work as newline from io.open() which supports only so called "legal" newlines which are: None, '', '\n', '\r', and '\r\n', or to allow users use any sequence as newline hence do replacing before passing text to io.open()?

It should work exactly as the newline argument of open(). Anything else would be surprising.

CLA signed now and PR is ready :)

 New changeset 5f227413400c4dfdba210cc0f8c9305421638bc1 by Максим in branch 'master': bpo-23706: Add newline parameter to pathlib.Path.write_text (GH-22420) (GH-22420) https://github.com/python/cpython/commit/5f227413400c4dfdba210cc0f8c9305421638bc1 

Thank you