Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder2.hal-mli.net!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!rt.uk.eu.org!news.mixmin.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.freenet.ag!news2.euro.net!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; 'modified': 0.05; 'modify': 0.05; 'python': 0.09; "'...'": 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'terry': 0.09; 'url:github': 0.09; 'cases': 0.15; "':'": 0.16; '1),': 0.16; 'feasible': 0.16; 'literals': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'rejected.': 0.16; 'subject:)?': 0.16; 'top- level': 0.16; 'url:issues': 0.16; 'wrote:': 0.17; 'yield': 0.17; 'jan': 0.18; 'discussion': 0.20; 'tuples': 0.22; 'idea': 0.24; 'header:In-Reply-To:1': 0.25; 'header:User-Agent:1': 0.26; 'skip:" 20': 0.26; 'header:X-Complaints-To:1': 0.28; 'yields': 0.29; 'objects': 0.29; 'probably': 0.29; 'at:': 0.31; 'could': 0.32; 'to:addr:python-list': 0.33; 'pm,': 0.35; 'there': 0.35; 'received:org': 0.36; 'but': 0.36; 'subject: (': 0.36; 'does': 0.37; 'rather': 0.37; 'subject:: ': 0.38; 'instead': 0.39; 'to:addr:python.org': 0.39; 'hello,': 0.39; 'skip:" 10': 0.40; 'header:Received:5': 0.40; 'email addr:gmail.com': 0.63; 'more': 0.63; 'believe': 0.69; 'received:fios.verizon.net': 0.84; 'imagine': 0.96 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Terry Reedy Subject: Re: Suggested feature: slice syntax within tuples (or even more generally)? Date: Thu, 14 Feb 2013 00:23:07 -0500 References: <2e07acfb-4f48-4a27-9b06-3d8103325c0f@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: pool-173-75-251-66.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 In-Reply-To: <2e07acfb-4f48-4a27-9b06-3d8103325c0f@googlegroups.com> 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: 1360819410 news.xs4all.nl 6943 [2001:888:2000:d::a6]:50449 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:38842 On 2/13/2013 2:00 PM, stephenwlin@gmail.com wrote: > Hello, > > Would it be feasible to modify the Python grammar to allow ':' to generate slice objects everywhere rather than just indexers and top-level tuples of indexers? > > Right now in Py2.7, Py3.3: > "obj[:,2]" yields "obj[slice(None),2]" > but > "obj[(:,1),2]" is an error, instead of "obj[(slice(None), 1), 2]" > > Also, more generally, you could imagine this working in (almost?) any expression without ambiguity: > "a = (1:2)" could yield "a = slice(1,2)" I believe the idea of slice literals has been rejected. > See motivating discussion for this at: > https://github.com/pydata/pandas/issues/2866 > > There might not be very many use cases for this currently outside of pandas, but apparently the grammar was already modified to allow '...' outside indexers and there's probably even fewer valid use cases for that: > "e = ..." yields "e = Ellipsis" One dubious move does not justify another. -- Terry Jan Reedy