[Idle-dev] [ idlefork-Bugs-661759 ] IDLE should preserve source files' newline conventions

[SourceForge.net]

Bugs item #661759, was opened at 2003-01-03 13:11
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109579&aid=661759&group_id=9579

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Andrew Koenig (arkoenig)
Assigned to: Nobody/Anonymous (nobody)
Summary: IDLE should preserve source files' newline conventions

Initial Comment:
If I move a Unix source file to a Windows system (or
vice versa) and use IDLE to edit the file, the changed
file acquires the newline convention of its new host. 
This behavior, though logical, is inconvenient in
heterogeneous environments.

I would like to suggest that when IDLE opens a source
file, it should determine what newline convention the
file uses and preserve that convention when it updates
the file.


----------------------------------------------------------------------

>Comment By: Kurt B. Kaiser (kbk)
Date: 2003-01-03 14:59

Message:
Logged In: YES 
user_id=149084

** GvR Idle-dev:
Until recently this would have been a pain.  As of Python 2.3, it can be done quite conveniently using universal newlines, open(filename,"U"), and the new 'newlines' attribute of resulting file objects.
==========

I suppose that since IDLEfork supports 2.2 that this would be 
deferred until after the merge?
KBK

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109579&aid=661759&group_id=9579