Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2.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.029 X-Spam-Evidence: '*H*': 0.94; '*S*': 0.00; 'syntax': 0.04; 'yeah,': 0.09; 'python': 0.11; '(syntax': 0.16; 'all?': 0.16; 'bracket,': 0.16; 'brackets': 0.16; 'from:addr:cs': 0.16; 'from:addr:zip.com.au': 0.16; 'from:name:cameron simpson': 0.16; 'message-id:@cskk.homeip.net': 0.16; 'received:211.29': 0.16; 'received:211.29.132': 0.16; 'received:optusnet.com.au': 0.16; 'received:syd.optusnet.com.au': 0.16; 'simpson': 0.16; 'subject:Problem': 0.16; 'sure.': 0.16; 'wrote:': 0.18; 'header :User-Agent:1': 0.23; 'error': 0.23; '(or': 0.24; 'header:In- Reply-To:1': 0.27; 'feature': 0.29; 'yes.': 0.31; 'quite': 0.32; 'actual': 0.34; 'subject:the': 0.34; 'subject:with': 0.35; 'editor': 0.35; 'but': 0.35; 'received:com.au': 0.36; 'charset:us- ascii': 0.36; 'thanks': 0.36; "i'll": 0.36; 'skip:o 20': 0.38; 'received:211': 0.38; 'same.': 0.38; 'to:addr:python-list': 0.38; 'that,': 0.38; 'subject:" ': 0.39; 'to:addr:python.org': 0.39; 'is.': 0.60; 'content-disposition:inline': 0.62; 'kind': 0.63; 'more': 0.64; 'close': 0.67; 'line,': 0.68; 'grew': 0.84; 'more?': 0.84; 'technique.': 0.84; 'mistake': 0.91; 'imagine': 0.93; '2013': 0.98 Date: Fri, 21 Jun 2013 08:38:29 +1000 From: Cameron Simpson To: python-list@python.org Subject: Re: Problem with the "for" loop syntax MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) References: X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.0 cv=eqSHVfVX c=1 sm=1 a=wom5GMh1gUkA:10 a=GZs24lQ_rmAA:10 a=kj9zAlcOel0A:10 a=vrnE16BAAAAA:8 a=ZtCCktOnAAAA:8 a=0n0nKMa5IkwA:10 a=pGLkceISAAAA:8 a=Nuhngmydyyb35PfeID4A:9 a=CjuIK1q_8ugA:10 a=MSl-tDqOz04A:10 a=ChdAjXE5lkUvdteQbhpnkQ==:117 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: 26 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1371769351 news.xs4all.nl 15922 [2001:888:2000:d::a6]:57738 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:48828 On 20Jun2013 13:55, Neil Cerutti wrote: | On 2013-06-20, Joshua Landau wrote: | > On 20 June 2013 04:11, Cameron Simpson wrote: | >> Also, opening-and-not-closing a set of brackets is almost the | >> only way in Python to make this kind of error (syntax at one | >> line, actual mistake far before). | >> | >> See if your editor has a show-the-matching-bracket mode. | >> If you suspect you failed to close a bracket, one approach is | >> to go _below_ the syntax error (or right on it) and type a | >> closing bracket. Then see where the editor thinks the opening | >> one is. | > | > Thanks for that, that's quite an ingenious technique. | | The auto-indent feature of Vim catches this type of syntax error, | and I imagine other good autoindent support will do the same. Interesting. I use autoindent but grew up with it for prose. I hadn't realised vim's support inderstaood python indentation. I'll have to pay more attention... -- Cameron Simpson Do I have it all? Yes. Do I want more? Yeah, sure. - Demi Moore