Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!feeder.news-service.com!news2.euro.net!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!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; 'python,': 0.01; 'subject:: [': 0.03; 'mrab': 0.04; ':-)': 0.06; 'subject:Python': 0.06; 'python': 0.08; 'accidental': 0.09; 'clearly,': 0.09; 'imho.': 0.09; 'readable': 0.09; 'received:209.85.160.174': 0.09; 'received :mail-gy0-f174.google.com': 0.09; 'syntax.': 0.09; 'subject:] ': 0.14; 'case.': 0.15; 'great.': 0.15; 'heavily': 0.15; "';'": 0.16; 'downside,': 0.16; 'lan': 0.16; 'magnitude.': 0.16; 'optimizing': 0.16; 'semicolon': 0.16; 'semicolons': 0.16; 'sizable': 0.16; 'syntactical': 0.16; 'workaround': 0.16; 'syntax': 0.16; 'wrote:': 0.16; "wouldn't": 0.17; 'wed,': 0.17; '>>>': 0.18; 'sfxlen:2': 0.19; 'programming': 0.20; "we'd": 0.21; 'cc:2**0': 0.22; 'header :In-Reply-To:1': 0.22; '(or': 0.23; 'indentation': 0.23; 'optional': 0.23; 'pm,': 0.24; 'changed': 0.24; 'aug': 0.24; "python's": 0.24; "i'm": 0.27; 'thu,': 0.28; 'url:mailman': 0.28; 'message-id:@mail.gmail.com': 0.29; 'cc:addr:python.org': 0.30; 'lines': 0.30; 'skip:_ 40': 0.31; 'chris': 0.32; 'list': 0.32; 'coding': 0.32; 'source': 0.33; 'to:addr:python-list': 0.33; 'url:listinfo': 0.33; 'majority': 0.34; 'languages.': 0.34; 'received:209.85.160': 0.35; 'core': 0.36; 'url:python': 0.36; 'but': 0.37; 'think': 0.38; 'received:google.com': 0.38; 'url:org': 0.38; 'received:209.85': 0.38; 'should': 0.38; 'to:addr:python.org': 0.39; 'case': 0.39; 'mailing': 0.39; 'more': 0.60; 'free': 0.63; 'noise': 0.67; '11,': 0.68; 'glad': 0.70; 'subject:line': 0.73; 'gain': 0.74; 'omission': 0.84; 'structures.': 0.84 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=Gxb5+l4xOGcqFTKtC5YbpPnjGxKfDURwn31Oikw5CsE=; b=YVg4cF00AXjFFdE8+YMYoPiqlnZFHNwITW93LunB/+jlQ7DjOv6W8+x1Hc7PmlFQbZ oHPW95ht8NqknvO66jeLgNu3aZPzebaX79PChUrEOcOCNzll02XWeYqVrVSOoKXKBWdQ nOH9e3ivpAkzU/9BJ1RmvyVO8Y0WJ1kFMuWwQ= MIME-Version: 1.0 In-Reply-To: <4E43D2F2.1090004@mrabarnett.plus.com> References: <1312951356.77394.YahooMailNeo@web121518.mail.ne1.yahoo.com> <4e424208$0$29965$c3e8da3$5496439d@news.astraweb.com> <1312981104.89312.YahooMailNeo@web121520.mail.ne1.yahoo.com> <1312982377.95657.YahooMailNeo@web121508.mail.ne1.yahoo.com> <1313031175.38817.YahooMailNeo@web121515.mail.ne1.yahoo.com> <4E43D2F2.1090004@mrabarnett.plus.com> From: Matt Joiner Date: Fri, 12 Aug 2011 00:28:04 +1000 Subject: Re: [Python-ideas] allow line break at operators To: python-list@python.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: python-ideas X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 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: 55 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1313072908 news.xs4all.nl 23888 [2001:888:2000:d::a6]:43583 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:11218 +0.5 The "trailing \" workaround is nonobvious. Wrapping in () is noisy and already heavily used by other syntactical structures. Since a final ':' is needed anyway, i think this would be great. if a and b or c: do stuff() On Thu, Aug 11, 2011 at 11:02 PM, MRAB wrote: > On 11/08/2011 05:16, Chris Rebert wrote: >> >> On Wed, Aug 10, 2011 at 7:52 PM, Yingjie Lan =C2=A0wr= ote: >>> >>> :And if we require {} then truly free indentation should be OK too! But >>> >>> :it wouldn't be Python any more. >>> >>> Of course, but not the case with ';'. Currently ';' is optional in >>> Python, >> >> I think of it more as that Python deigns to permit semicolons. >> >>> But '{' is used for dicts. Clearly, ';' and '{' are different in >>> magnitude. >>> >>> So the decision is: shall we change ';' from optional to mandatory >>> to allow free line splitting? >> >> Hell no, considering that the sizable majority of lines *aren't* >> split, which makes those semicolons completely redundant to their >> accompanying newlines. We'd be practicing poor Huffman coding by >> optimizing for the *un*common case. It would also add punctuational >> noise to what is otherwise an amazingly clean and readable syntax. >> Accidental semicolon omission is (IMO) the most irritating source of >> syntax (and, inadvertently, sometimes other more serious) errors in >> curly-braced programming languages. >> > +1 >> >> Such a core syntax feature is not going to be changed lightly (or likely >> ever). >> > I'm glad to hear that. :-) > > Although Python's use of indentation has its downside, we gain much > more then we lose, IMHO. > _______________________________________________ > Python-ideas mailing list > Python-ideas@python.org > http://mail.python.org/mailman/listinfo/python-ideas >