Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed3.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.001 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'that?': 0.05; 'subject:Python': 0.06; 'fixes': 0.07; 'defines': 0.09; 'oh,': 0.09; 'pep': 0.09; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'subject:language': 0.09; 'python': 0.11; 'bug': 0.12; 'jan': 0.12; '2.7': 0.14; 'bugs.': 0.16; 'patches': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'subject: \n ': 0.16; 'apps': 0.16; 'wrote:': 0.18; 'header:User-Agent:1': 0.23; 'developers': 0.25; 'header:X -Complaints-To:1': 0.27; 'header:In-Reply-To:1': 0.27; 'am,': 0.29; 'subject:list': 0.30; 'code': 0.31; 'becoming': 0.31; "d'aprano": 0.31; 'fixing': 0.31; 'steven': 0.31; 'probably': 0.32; 'another': 0.32; 'worked': 0.33; 'announce': 0.33; 'core': 0.34; 'maybe': 0.34; 'idle': 0.36; 'to:addr:python-list': 0.38; 'bad': 0.39; 'sure': 0.39; 'to:addr:python.org': 0.39; 'received:org': 0.40; 'how': 0.40; 'break': 0.61; 'received:173': 0.61; 'finally': 0.65; 'internet': 0.71; 'subject:this': 0.83; '2015': 0.84; 'citizens.': 0.84; 'received:fios.verizon.net': 0.84; 'dare': 0.91 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Terry Reedy Subject: Re: Explanation of this Python language feature? [x for x in x for x in x] (to flatten a nested list) Date: Sat, 05 Apr 2014 07:20:24 -0400 References: <9daf0806-02de-4447-964c-c8f8953c23e5@googlegroups.com> <5334c38e$0$29994$c3e8da3$5496439d@news.astraweb.com> <53364327$0$29994$c3e8da3$5496439d@news.astraweb.com> <53365F55.2040302@gmail.com> <533836c4$0$29994$c3e8da3$5496439d@news.astraweb.com> <8eaca90c-cd43-40b7-92c3-ad8676a11cbd@googlegroups.com> <533fd894$0$29993$c3e8da3$5496439d@news.astraweb.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-254-207.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 In-Reply-To: <533fd894$0$29993$c3e8da3$5496439d@news.astraweb.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: 17 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1396696847 news.xs4all.nl 2967 [2001:888:2000:d::a6]:42454 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:69730 On 4/5/2014 6:19 AM, Steven D'Aprano wrote: > Oh, I dare say that when the core developers finally announce Python 2.7 > is end-of-lifed, probably in another five or so years, Bug fixing will end in May/June 2015 with 2.7.8, maybe 2.7.9. It will probably start tapering off before that on the basis that fixes may break working code that has worked around bugs. I am not sure how long I will backport Idle patches. Code-only security patches after that? Undecided. I think PEP 466 defines what the focus will be -- keeping 2.7 web apps from becoming bad internet citizens. -- Terry Jan Reedy