From owner-freebsd-python@FreeBSD.ORG Mon Aug 5 08:20:42 2013 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DBB413ED for ; Mon, 5 Aug 2013 08:20:42 +0000 (UTC) (envelope-from mva@freebsd.org) Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de [80.67.31.98]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 99F462E6C for ; Mon, 5 Aug 2013 08:20:42 +0000 (UTC) Received: from [80.67.16.118] (helo=webmailfront01.ispgateway.de) by smtprelay05.ispgateway.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1V6G1S-0004DI-1f for freebsd-python@freebsd.org; Mon, 05 Aug 2013 10:20:10 +0200 Received: from his1.his.de (his1.his.de [192.124.237.237]) by webmail.df.eu (Horde Framework) with HTTP; Mon, 05 Aug 2013 10:20:10 +0200 Date: Mon, 05 Aug 2013 10:20:10 +0200 Message-ID: <20130805102010.Horde.z0Uqk2RXOt3D3TAm6Wn3Fw1@webmail.df.eu> From: Marcus von Appen To: freebsd-python@freebsd.org Subject: Re: Naming of lang/pypy and lang/pypy3 References: <1595859.oJfAmeEhYc@dragon.dg> <20130801195023.GA1345@medusa.sysfault.org> <6283190.FdUAYIpsqz@dragon.dg> In-Reply-To: <6283190.FdUAYIpsqz@dragon.dg> User-Agent: Internet Messaging Program (IMP) H5 (6.0.4) Content-Type: text/plain; charset=UTF-8; format=flowed; DelSp=Yes MIME-Version: 1.0 Content-Disposition: inline X-Df-Sender: ZnJlZWJzZEBzeXNmYXVsdC5vcmc= X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: mva@freebsd.org List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 08:20:42 -0000 David Naylor : [...] > > Could you please elaborate how the beta's are preventing pypy from being used > as a replacement for CPython? If I would provide and maintain a production environment, in which stability and reliability is important for my customers, I would not install any software classified as beta as long as there is no important reason to do otherwise (and even a non-beta release would require heaps of testing). Not because a non-beta release is better or more stable, but because I am in a bad position for discussion with the customers, if something goes really wrong with the beta, regardless of how well it was tested. Just my 2 cents :) Cheers Marcus