Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.mixmin.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed2a.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; 'english.': 0.04; 'interpreter': 0.05; 'subject:Python': 0.06; 'correct.': 0.07; "'python": 0.09; 'english,': 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; 'jan': 0.12; '3.0.': 0.16; 'did.': 0.16; 'discussion?': 0.16; 'fine.': 0.16; 'python3.': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'sense,': 0.16; 'subject: \n ': 0.16; 'unicode.': 0.16; 'wrote:': 0.18; 'code.': 0.18; 'meant': 0.20; '>>>': 0.22; 'header:User-Agent:1': 0.23; '2.2': 0.24; 'unicode': 0.24; 'question': 0.24; 'developers': 0.25; 'suggested': 0.26; 'read,': 0.26; 'header:X-Complaints- To:1': 0.27; 'header:In-Reply-To:1': 0.27; 'subject:list': 0.30; 'asked': 0.31; 'getting': 0.31; '>>>>': 0.31; 'apparently': 0.31; 'use?': 0.31; 'class': 0.32; 'text': 0.33; 'running': 0.33; '"the': 0.34; 'core': 0.34; 'common': 0.35; 'something': 0.35; 'add': 0.35; 'really': 0.36; 'are,': 0.36; 'right?': 0.36; "didn't": 0.36; 'useful': 0.36; 'starting': 0.37; 'question,': 0.38; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'does': 0.39; 'to:addr:python.org': 0.39; 'enough': 0.39; 'either': 0.39; 'received:org': 0.40; 'most': 0.60; 'introduced': 0.61; 'no.': 0.61; 'received:173': 0.61; 'our': 0.64; 'became': 0.64; 'become': 0.64; 'american': 0.66; 'production': 0.68; 'default': 0.69; 'subject:this': 0.83; 'answer:': 0.84; 'received:fios.verizon.net': 0.84; 'speak,': 0.84 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: Tue, 01 Apr 2014 18:33:25 -0400 References: <9daf0806-02de-4447-964c-c8f8953c23e5@googlegroups.com> <87ior3w740.fsf@elektro.pacujo.net> <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> 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: 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: 44 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1396532123 news.xs4all.nl 2891 [2001:888:2000:d::a6]:57827 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:69576 On 4/1/2014 5:26 PM, Mark H Harris wrote: >>>>> I didn't really start using unicode >>>>> until about 5 years ago; python has only really used it since python3. >>>>> right? If you narrowly meant "The python interpreter only starting using unicode as the default text class in 3.0", then you are, in that narrow sense, correct. If you meant something broader, if by 'python' you meant 'the python community' or 'python programmers', then you are wrong. >>>> No. Python 2.2 introduced Unicode. 2.0, as someone else corrected. >>> I didn't ask when it was introduced, I asked when it became useful? It was useful immediately when introduced. Do you really think we would add something useless, and that no one wanted to use? Core developers constantly ask 'What is the practical use case?' in response to suggested additions. For either question, your original answer is wrong. >> No you didn't. Does not matter. The answer he gave to the question he claims he asked, and the elaboration below, is wrong. > Yes, I did. Fine. You asked 'When did unicode in Python become useful.' Answer: 2.0, not 3.0. Most unicode use in Python is still running on Python 2. It works well enough that people are reluctant to migrate working and tested production code. End of discussion? > Our common English is apparently getting in the way. > Well, I speak American English, and you don't, apparently; U.K.? I hear, speak, read, and write standard American English. -- Terry Jan Reedy