Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.albasani.net!rt.uk.eu.org!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!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.015 X-Spam-Evidence: '*H*': 0.97; '*S*': 0.00; 'encoding': 0.05; 'subject:Python': 0.06; 'apps,': 0.07; 'exception.': 0.09; 'happen.': 0.09; 'python': 0.11; 'thread': 0.14; 'windows': 0.15; 'expert,': 0.16; 'from:addr:torriem': 0.16; 'from:name:michael torrie': 0.16; 'sane': 0.16; 'specifying': 0.16; 'wrote:': 0.18; 'thanks.': 0.20; 'seems': 0.21; 'putting': 0.22; 'print': 0.22; 'header:User-Agent:1': 0.23; 'unicode': 0.24; 'question': 0.24; 'header:In-Reply-To:1': 0.27; 'am,': 0.29; 'character': 0.29; 'characters': 0.30; 'important.': 0.30; "i'm": 0.30; 'code': 0.31; 'posting': 0.31; 'continually': 0.31; 'option': 0.32; 'cases': 0.33; 'comment': 0.34; 'could': 0.34; 'convert': 0.35; 'no,': 0.35; 'but': 0.35; 'really': 0.36; 'useful': 0.36; 'list.': 0.37; 'being': 0.38; 'message-id:@gmail.com': 0.38; 'to:addr:python- list': 0.38; 'issue': 0.38; 'to:addr:python.org': 0.39; 'either': 0.39; 'received:org': 0.40; 'skip:u 10': 0.60; 'email addr:gmail.com': 0.63; 'such': 0.63; 'myself': 0.63; 'more': 0.64; 'anything.': 0.68; 'caused': 0.69; 'led': 0.72; 'behavior': 0.77; 'confusing': 0.84; 'silently': 0.84 X-Virus-Scanned: amavisd-new at torriefamily.org Date: Mon, 14 Jul 2014 21:58:05 -0600 From: Michael Torrie User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131118 Thunderbird/17.0.11 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Python 3 is killing Python References: <57ajo9poljjre4c4ig0n0ss8kph8k78lp0@4ax.com> <5389cb53$0$29978$c3e8da3$5496439d@news.astraweb.com> <99b7b2a2-7521-42d7-a5a0-1a35d4d5b922@googlegroups.com> <2d66f199-ceea-4cfe-b35f-436041398817@googlegroups.com> In-Reply-To: <2d66f199-ceea-4cfe-b35f-436041398817@googlegroups.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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: 1405396693 news.xs4all.nl 2929 [2001:888:2000:d::a6]:41824 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:74461 On 06/03/2014 12:12 AM, wxjmfauth@gmail.com wrote: > I was myself really suprised to fall on such a case and > after thinking no, such cases may logically happen. Putting in this comment not for JMF but for poor souls who find this thread on a search and are led astray by jmf's trolling. Either it was your code or an issue with the Windows console that caused the exception. When you try to print out unicode strings, Python must convert them to the character encoding of the terminal in order to print them out. On sane systems this is UTF-8. On Windows it could be anything. Do you want Python to fail silently or do you want to fail with a useful message, with the option of specifying the exact behavior you want (replace unrepresentable characters with spaces, question marks, etc)? Seems like jmf, though being a self-proclaimed unicode expert, continually confusing unicode with encoding schemes. > > It's not important. I'm no more writing Py apps, only > considering software through an unicode eye. Please just stop posting to this list. thanks.