Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!feeds.phibee-telecom.net!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'resulting': 0.04; 'url:launchpad': 0.05; '-*-': 0.07; 'utf-8': 0.07; 'string': 0.09; 'coding:': 0.09; 'if,': 0.09; 'indeed,': 0.09; 'newline': 0.09; 'windows,': 0.09; 'cc:addr:python-list': 0.11; 'def': 0.12; 'windows': 0.15; "'w')": 0.16; '23,': 0.16; 'carriage': 0.16; 'cc:name:python list': 0.16; 'dump': 0.16; 'from:addr:swing.be': 0.16; 'from:addr:vincent.vandevyvre': 0.16; 'from:name:vincent vande vyvre': 0.16; 'line),': 0.16; 'message-id:@swing.be': 0.16; 'newlines': 0.16; 'oqapy': 0.16; 'paqager': 0.16; 'received:mobistar.be': 0.16; 'url:oqapy': 0.16; 'url:paqager': 0.16; 'url:qarte': 0.16; 'v.v.': 0.16; '\xe9crit': 0.16; 'wrote:': 0.18; 'do.': 0.18; 'bit': 0.19; 'file,': 0.19; 'later': 0.20; 'seems': 0.21; '>>>': 0.22; 'example': 0.22; 'import': 0.22; 'cc:addr:python.org': 0.22; 'header:User-Agent:1': 0.23; 'replace': 0.24; 'file.': 0.24; 'cc:2**0': 0.24; "i've": 0.25; 'source': 0.25; 'script': 0.25; 'changes,': 0.26; 'this:': 0.26; 'code:': 0.26; 'somewhere': 0.26; 'header:In-Reply-To:1': 0.27; 'skip:- 40': 0.29; 'am,': 0.29; 'unix': 0.29; 'characters': 0.30; 'compared': 0.30; 'converting': 0.30; 'dos': 0.30; 'code': 0.31; '(since': 0.31; 'equivalent.': 0.31; 'strip': 0.31; 'txt': 0.31; 'file': 0.32; 'skip:- 30': 0.32; 'text': 0.33; 'open': 0.33; 'screen': 0.34; 'subject:with': 0.35; 'created': 0.35; 'problem.': 0.35; 'something': 0.35; 'but': 0.35; 'there': 0.35; 'sequence': 0.36; 'doing': 0.36; 'should': 0.36; 'two': 0.37; 'skip:o 20': 0.38; 'jason': 0.38; 'files': 0.38; 'hope': 0.61; 'first': 0.61; "you've": 0.63; 'therefore,': 0.64; 'more': 0.64; 'jul': 0.74; 'ending': 0.78; 'whereas': 0.91; 'to:none': 0.92; 'imagine': 0.93; '2013': 0.98 Date: Tue, 23 Jul 2013 15:10:35 +0200 From: Vincent Vande Vyvre User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 MIME-Version: 1.0 CC: python list Subject: Re: Strange behaviour with os.linesep References: <368qu85msgfhuk2j2s13qj0bqn4rkcint9@4ax.com> <51ED3CEB.1070706@gmail.com> <51EE6C15.5070701@swing.be> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 105 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1374585496 news.xs4all.nl 15890 [2001:888:2000:d::a6]:32924 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:51086 Le 23/07/2013 14:39, Jason Swails a écrit : > > > > On Tue, Jul 23, 2013 at 7:42 AM, Vincent Vande Vyvre > > wrote: > > On Windows a script where de endline are the system line sep, the > files are open with a double line in Eric4, Notepad++ or Gedit but > they are correctly displayed in the MS Bloc-Notes. > > Example with this code: > ---------------------------------------------- > # -*- coding: utf-8 -*- > > import os > L_SEP = os.linesep > > def write(): > strings = ['# -*- coding: utf-8 -*-\n', > 'import os\n', > 'import sys\n'] > with open('writetest.py', 'w') as outf: > for s in strings: > outf.write(s.replace('\n', L_SEP)) > > > I must ask why you are setting strings with a newline line ending only > to replace them later with os.linesep. This seems convoluted compared > to doing something like > > def write(): > strings = ['#-*- coding: utf-8 -*-', 'import os', 'import sys'] > with open('writetest.py', 'w') as outf: > for s in strings: > outf.write(s) > outf.write(L_SEP) > > Or something equivalent. > > If, however, the source strings come from a file you've created > somewhere (and are loaded by reading in that file line by line), then > I can see a problem. DOS line endings are carriage returns ('\r\n'), > whereas standard UNIX files use just newlines ('\n'). Therefore, if > you are using the code: > > s.replace('\n', L_SEP) > > in Windows, using a Windows-generated file, then what you are likely > doing is converting the string sequence '\r\n' into '\r\r\n', which is > not what you want to do. I can imagine some text editors interpreting > that as two endlines (since there are 2 \r's). Indeed, when I execute > the code: > > >>> l = open('test.txt', 'w') > >>> l.write('This is the first line\r\r\n') > >>> l.write('This is the second\r\r\n') > >>> l.close() > > on UNIX and open the resulting file in gedit, it is double-spaced, but > if I just dump it to the screen using 'cat', it is single-spaced. > > If you want to make your code a bit more cross-platform, you should > strip out all types of end line characters from the strings before you > write them. So something like this: > > with open('writetest.py', 'w') as outf: > for s in strings: > outf.write(s.rstrip('\r\n')) > outf.write(L_SEP) > > Hope this helps, > Jason The '\n' are in the original file. I've tested these other versions: ------------------------------- def write(): strings = ['# -*- coding: utf-8 -*-\n', 'import os\n', 'import sys\n'] with open('writetest.py', 'w') as outf: txt = L_SEP.join([s.rstip() for s in strings]): outf.write(txt) ------------------------------ ------------------------------- def write(): strings = ['# -*- coding: utf-8 -*-', 'import os', 'import sys'] with open('writetest.py', 'w') as outf: txt = L_SEP.join( strings): outf.write(txt) ------------------------------ Las, no changes, always correctly displayed in MS bloc-notes but with double line in other éditors. -- Vincent V.V. Oqapy . Qarte . PaQager