Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed4a.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; 'subject:Python': 0.06; 'killer': 0.07; 'python3': 0.07; 'from:addr:ethan': 0.09; 'from:addr:stoneleaf.us': 0.09; 'from:name:ethan furman': 0.09; 'message-id:@stoneleaf.us': 0.09; '~ethan~': 0.09; 'subject:How': 0.10; 'python': 0.11; '24,': 0.16; 'backwards': 0.16; 'bespoke': 0.16; 'python3.': 0.16; 'reinvent': 0.16; 'ties': 0.16; 'sat,': 0.16; 'wrote:': 0.18; 'library': 0.18; 'trying': 0.19; 'seems': 0.21; 'header:User-Agent:1': 0.23; 'focusing': 0.24; '(for': 0.26; 'header:In-Reply-To:1': 0.27; 'am,': 0.29; 'work.': 0.31; 'app.': 0.31; 'libraries': 0.31; 'please.': 0.31; 'critical': 0.32; 'there': 0.35; 'charset:us-ascii': 0.36; 'bringing': 0.38; 'to:addr:python-list': 0.38; 'rather': 0.38; 'to:addr:python.org': 0.39; 'even': 0.60; 'most': 0.60; 'new': 0.61; 'save': 0.62; 'worth': 0.66; 'brand': 0.72; 'forward,': 0.84; 'thing,': 0.91 Date: Sat, 24 May 2014 12:08:47 -0700 From: Ethan Furman User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: python-list@python.org Subject: Re: How keep Python 3 moving forward References: <87tx8fh50a.fsf@elektro.pacujo.net> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator3304.hostgator.com X-AntiAbuse: Original Domain - python.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - stoneleaf.us X-BWhitelist: no X-Source-IP: 70.199.136.50 X-Exim-ID: 1WoHJI-0005DD-KV X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: ([192.168.43.29]) [70.199.136.50]:1382 X-Source-Auth: ethan+stoneleaf.us X-Email-Count: 1 X-Source-Cap: dG9idWs7dG9idWs7Z2F0b3IzMzA0Lmhvc3RnYXRvci5jb20= 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: 20 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1400959892 news.xs4all.nl 2970 [2001:888:2000:d::a6]:38638 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:71967 On 05/24/2014 09:03 AM, Devin Jeanpierre wrote: > On Sat, May 24, 2014 at 2:59 AM, Marko Rauhamaa wrote: >> >> Instead of focusing on bringing legacy libraries to Python3 (for which >> there never seems to be a critical need), Python3 needs a brand new >> killer module/application/library that is only available on Python3. > > Yikes! Backwards incompatibility is a poor excuse for NIH syndrome. > > Don't reinvent the wheel, please. If there's an existing > implementation of a thing, that can save you a lot of work. Even if it > ties you to Python 2, that's worth it, most of the time. If you want > to migrate to Python 3, help that library forward, rather than trying > to make some bespoke replacement you think will be a killer app. +1 -- ~Ethan~