Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed1.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.001 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'python,': 0.02; 'cpython': 0.05; 'interpreter': 0.05; 'compiler': 0.07; 'pypy': 0.07; 'received:80.91': 0.09; 'received:80.91.229': 0.09; 'received:gmane.org': 0.09; 'received:list': 0.09; 'jan': 0.12; '7:45': 0.16; 'knock': 0.16; 'libraries.': 0.16; 'numpy': 0.16; 'received:80.91.229.3': 0.16; 'received:plane.gmane.org': 0.16; 'reedy': 0.16; 'subject:Pypy': 0.16; 'time-saving': 0.16; 'units,': 0.16; 'wrote:': 0.18; 'seems': 0.21; 'saying': 0.22; 'this?': 0.23; 'header:User-Agent:1': 0.23; "i've": 0.25; 'developing': 0.27; 'header:X-Complaints-To:1': 0.27; 'header:In- Reply-To:1': 0.27; 'tried': 0.27; 'am,': 0.29; 'quickly': 0.29; "doesn't": 0.30; 'libraries': 0.31; 'moment': 0.34; 'maybe': 0.34; "can't": 0.35; 'display': 0.35; 'anybody': 0.35; 'but': 0.35; 'really': 0.36; 'useful': 0.36; 'subject:?': 0.36; 'to:addr :python-list': 0.38; 'rather': 0.38; 'recent': 0.39; 'to:addr:python.org': 0.39; 'enough': 0.39; 'received:org': 0.40; 'even': 0.60; 'future': 0.60; 'dave': 0.60; 'range': 0.61; 'simply': 0.61; 'complete': 0.62; 'making': 0.63; 'more': 0.64; 'results': 0.69; 'felt': 0.74; 'quicker': 0.84; 'received:fios.verizon.net': 0.84 X-Injected-Via-Gmane: http://gmane.org/ To: python-list@python.org From: Terry Reedy Subject: Re: Future of Pypy? Date: Mon, 23 Feb 2015 01:34:19 -0500 References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Gmane-NNTP-Posting-Host: pool-98-114-97-173.phlapa.fios.verizon.net User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.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: 29 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1424673270 news.xs4all.nl 2952 [2001:888:2000:d::a6]:53481 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:86197 On 2/22/2015 7:45 AM, Dave Farrance wrote: > As an engineer, I can quickly knock together behavioural models of > electronic circuits, complete units, and control systems in Python, then > annoyingly in a few recent cases, have to re-write in C for speed. > > I've tried PyPy, the just-in-time compiler for Python, and that is > impressively, hugely fast in comparison, but it's no good making these > models if I can't display the results in a useful way, and at the moment > PyPy just doesn't have the huge range of useful time-saving libraries that > CPython has. It's still quicker to do a re-write in the more cumbersome C > than try to work with PyPy because C, like CPython, also has many useful > libraries. > > A few years back, I recall people saying that PyPy was going to be the > future of Python, but it seems to me that CPython still has the lion's > share of the momentum, is developing faster and has ever more libraries, > while PyPy is struggling to get enough workers to even get Numpy > completed. > > Maybe there's not enough people like me that have really felt the need for > the speed. Or maybe it's simply the accident of the historical > development path that's set-in-stone an interpreter rather than a JIT. > Anybody got a useful perspective on this? > -- Terry Jan Reedy