Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!newsfeed.xs4all.nl!newsfeed4a.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.005 X-Spam-Evidence: '*H*': 0.99; '*S*': 0.00; 'received:134': 0.05; 'subject:Python': 0.06; 'context': 0.07; 'extent': 0.07; 'so?': 0.09; 'subject:language': 0.09; 'python': 0.11; 'language,': 0.12; 'language.': 0.14; '10:54,': 0.16; 'contexts,': 0.16; 'readable': 0.16; 'subject: \n ': 0.16; 'subject:?)': 0.16; 'subject:unicode': 0.16; 'symbols': 0.16; 'written.': 0.16; 'language': 0.16; 'wrote:': 0.18; 'bit': 0.19; 'written,': 0.19; 'programming': 0.22; 'header:User-Agent:1': 0.23; 'mathematical': 0.24; "shouldn't": 0.24; 'header:In-Reply-To:1': 0.27; 'chris': 0.29; 'code': 0.31; 'easier': 0.31; 'too.': 0.31; '25,': 0.31; 'anyone': 0.31; 'but': 0.35; 'should': 0.36; 'to:addr:python-list': 0.38; 'pm,': 0.38; 'little': 0.38; 'bad': 0.39; 'to:addr:python.org': 0.39; 'read': 0.60; 'matter': 0.61; 'skip:* 10': 0.61; 'first': 0.61; 'times': 0.62; 'making': 0.63; 'such': 0.63; 'more': 0.64; 'worth': 0.66; 'mar': 0.68; 'subject:this': 0.83; 'borrow': 0.84; 'pardon': 0.84 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAAdcMVOGuA9G/2dsb2JhbABZhx+/Y4E2gxkBAQEEIw8BRRELGAICBRYLAgIJAwIBAgFFEwYCAod1rEabZoZbF4EpjUcWglmBSQSYTYY1i32Bb4E/ Date: Tue, 25 Mar 2014 11:38:38 +0100 From: Antoon Pardon User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Icedove/24.3.0 MIME-Version: 1.0 To: python-list@python.org Subject: Re: Time we switched to unicode? (was Explanation of this Python language feature?) References: <9daf0806-02de-4447-964c-c8f8953c23e5@googlegroups.com> <532d5bd9$0$29994$c3e8da3$5496439d@news.astraweb.com> <0b78649a-16b3-4410-8258-e859578d62be@googlegroups.com> <281c8ce1-4f03-4e93-b5cd-d45b85e89e7e@googlegroups.com> <53314FC1.2010603@rece.vub.ac.be> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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: 1395743920 news.xs4all.nl 2839 [2001:888:2000:d::a6]:44997 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:69006 On 25-03-14 10:54, Chris Angelico wrote: > On Tue, Mar 25, 2014 at 8:43 PM, Antoon Pardon > wrote: >> I thought programs were read more than written. So if writing is made >> a bit more problematic but the result is more readable because we are >> able to use symbols that are already familiar from other contexts, I >> would say it is worth it. > It's a matter of extents. If code is read ten times for every time > it's written, making it twenty times harder to write and a little bit > easier to read is still a bad tradeoff. > > Also: To what extent IS that symbol familiar from some other context? > Are you using Python as a programming language, or should you perhaps > be using a mathematical front-end? Not everything needs to perfectly > match what anyone from any other context will expect. This is, first > and foremost, a *programming* language. So? We do use + -, so why shouldn't we use × for multiplication. Would such a use already indicate I should use a mathematical front-end? When a programming language is borrowing concepts from mathematics, I see no reason not to borrow the symbols used too. -- Antoon Pardon.