[Idle-dev] [ idlefork-Bugs-538584 ] IDLE needs to allow control of eol seq

[noreply@sourceforge.net]

Bugs item #538584, was opened at 2002-04-03 01:18
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=109579&aid=538584&group_id=9579

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: IDLE needs to allow control of eol seq

Initial Comment:
IDLE tries to respect the end of line sequence of the 
platform it is running on. However, sometimes this 
isn't the correct behavior.

I want to use IDLE on Windows, but access files on a 
Samba share. These files are in turn used by Apache, 
and it's very picky about end-of-line. If the file has 
CR-LF, it won't execute it.

Any time I change a file with IDLE, it resets all the 
end of line sequences. This also fouls up the ability 
to diff files, or do CVS merges, because it's a global 
change.

IDLE should either (1) allow an explicit setting for 
EOL sequence, or (2) figure out what it is for a 
specific file and then write it out the same way.


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

>Comment By: Guido van Rossum (gvanrossum)
Date: 2002-05-20 07:00

Message:
Logged In: YES 
user_id=6380

Definitely a feature request. I'm sure both IDLE versions
have this issue. It will be possible to fix this in Python
2.3 by using the Universal Newlines feature (see PEP 278) --
that will let IDLE determine the original newline
convention. Writing back using that convention is then
(relatively) simple, using binary output mode. (But you'll
have to get the text from the Text widget a line at a time,
or do a global replace of \n with the line ending of
choice.)

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

Comment By: Stephen M. Gava (elguavas)
Date: 2002-05-19 22:52

Message:
Logged In: YES 
user_id=75867

This item talks about idle rather than idlefork, although I
think the behaviour is the same in both cases. Should this
be entered as a python idle bug, or perhaps "feature request"?

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

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