Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path: <python.list@tim.thechases.com>
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; 'c/c++': 0.05; 'onto': 0.05; 'python)': 0.05; 'subject:two': 0.07; 'braces': 0.09; 'line).': 0.09; 'reason.': 0.09; 'subject:string': 0.09; 'throw': 0.09; 'pm,': 0.10; 'am,': 0.14; 'wrote:': 0.14; '(either': 0.16; '(well,': 0.16; '-tkc': 0.16; 'angelico': 0.16; 'blender': 0.16; 'folding': 0.16; 'from:addr:python.list': 0.16; 'from:addr:tim.thechases.com': 0.16; 'from:name:tim chase': 0.16; 'indent': 0.16; 'message-id:@tim.thechases.com': 0.16; 'pointer,': 0.16; 'subject:lines': 0.16; 'subject:split': 0.16; 'two.': 0.16; 'cc:addr:python-list': 0.17; 'tue,': 0.17; 'please?': 0.19; 'otherwise,': 0.19; '(which': 0.20; 'header:In-Reply-To:1': 0.21; 'compared': 0.22; 'cc:2**0': 0.22; 'cc:no real name:2**0': 0.23; 'subject:code': 0.23; 'code': 0.24; '"this': 0.25; 'like.': 0.25; "i'm": 0.27; '(the': 0.28; 'seeing': 0.28; 'cc:addr:python.org': 0.30; 'second': 0.30; 'chase': 0.30; 'print': 0.31; 'does': 0.33; 'starting': 0.33; 'chris': 0.34; 'header:User-Agent:1': 0.35; 'difference': 0.37; '(to': 0.37; 'coding': 0.37; 'two': 0.37; 'run': 0.38; 'but': 0.38; 'though': 0.38; 'subject:: ': 0.38; 'received:209': 0.39; 'your': 0.60; 'huge': 0.62; '("this': 0.84; 'dictate': 0.84; 'point:': 0.84; 'rome,': 0.84; 'tastes': 0.84; 'render': 0.91; 'way)': 0.91; 'subject:long': 0.93
Date: Mon, 13 Jun 2011 18:03:03 -0500
From: Tim Chase <python.list@tim.thechases.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Chris Angelico <rosuav@gmail.com>
Subject: Re: split long string in two code lines
References: <4df681ae$0$2694$4fafbaef@reader1.news.tin.it>	<20110613215510.GP2322@point.cs.wisc.edu>	<4DF6903F.7000101@tim.thechases.com> <BANLkTikv0ZbWHdkS9G6JfuxGNLmR9c32Vg@mail.gmail.com>
In-Reply-To: <BANLkTikv0ZbWHdkS9G6JfuxGNLmR9c32Vg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - boston.accountservergroup.com
X-AntiAbuse: Original Domain - python.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - tim.thechases.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: python-list@python.org
X-BeenThere: python-list@python.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe: <http://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive: <http://mail.python.org/pipermail/python-list>
List-Post: <mailto:python-list@python.org>
List-Help: <mailto:python-list-request@python.org?subject=help>
List-Subscribe: <http://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups: comp.lang.python
Message-ID: <mailman.202.1308006192.11593.python-list@python.org>
Lines: 44
NNTP-Posting-Host: 82.94.164.166
X-Trace: 1308006192 news.xs4all.nl 49177 [::ffff:82.94.164.166]:49765
X-Complaints-To: abuse@xs4all.nl
Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:7569

On 06/13/2011 05:38 PM, Chris Angelico wrote:
> On Tue, Jun 14, 2011 at 8:33 AM, Tim Chase
> <python.list@tim.thechases.com>  wrote:
>>   print ("this is not "
>>     "such a huge line "
>>     "even though it has "
>>     "lots of text in it."
>>     )
>>
>>   print (
>>     "this is not "
>>     "such a huge line "
>>     "even though it has "
>>     "lots of text in it."
>>     )
>
> I'm not seeing the difference between these two. Pointer, please? *puzzled*

Sorry...tried to make that clear in the surrounding text.  The 
first one has the open-paren on the same line as the starting 
line of content-text; the second one just has "print (" on the 
first line without the text (which is on the following line).

> Related point: Do you indent the ) to the same level as the opening
> quote on each line, or do you backdent it to the level of the
> statement? And, does it (either way) feel like you're writing braces
> in C?

My personal tastes run to your first form (the close-paren at the 
same indent level as the text) which makes it easy to use Vim's 
indent-based folding the way I mostly like.  I do (well, 
"did"...I try to shirk C/C++ these days because I just feel so 
unproductive compared to coding in Python) the same in my own C 
code for the same reason.  But if employer-standards dictate 
otherwise, when in Rome, render onto Caesar (to throw two 
aphorisms in the blender :)

-tkc