From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1EE30139694 for ; Mon, 10 Apr 2017 21:46:08 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3264821C1F4; Mon, 10 Apr 2017 21:44:36 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id DA1BF21C180 for ; Mon, 10 Apr 2017 21:44:35 +0000 (UTC) Received: from [192.168.2.10] (85.253.85.240.cable.starman.ee [85.253.85.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: leio) by smtp.gentoo.org (Postfix) with ESMTPSA id 51667340988 for ; Mon, 10 Apr 2017 21:44:34 +0000 (UTC) Message-ID: <1491860670.23778.1.camel@gentoo.org> Subject: Re: [gentoo-dev] Reverse use of Python/Ruby versions From: Mart Raudsepp To: gentoo-dev@lists.gentoo.org Date: Tue, 11 Apr 2017 00:44:30 +0300 In-Reply-To: References: <8F38F35E-A4CE-4530-880C-E409E672F253@gentoo.org> <1491844472.1661.1.camel@gentoo.org> <1491847844.1661.10.camel@gentoo.org> <1491850630.3444.2.camel@gentoo.org> <1491853895.3444.4.camel@gentoo.org> <1491855684.3444.6.camel@gentoo.org> <1491856998.1661.14.camel@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Archives-Salt: fffbe40e-1c9a-4fbe-8e8b-98919aa70dac X-Archives-Hash: deb70b79fff6e6269c9287b8d146d607 Ühel kenal päeval, E, 10.04.2017 kell 17:33, kirjutas William L. Thomson Jr.: > Add a new Java version and recompiling packages with it, will also > immediately show breakage if any. > > If your saying Python code is of higher quality than Java. I would > digress heavily on that. You have leniency in python not being strong > typed. Lack of generics and stuff could only mean that could be > worse. > Relying on internals to handle data types for you. Which is why python modules can't just pretend to work with a newer python by merely happening to "compile" and install. It is not strongly typed and it does not involve a AOT phase (pyc is just a semi-binary representation of the source code really) and issues are not found unless properly tested at runtime or test suite. > Regardless of new eclass, the TARGETS remain. Things did not change > from a user perspective. Recently packaging some ebuilds, the > COMPAT/VERSION does not seem to have changed. Despite what ever > changes to the eclass. Users don't get unexpected failures, as things that are claimed to work with a given python version, probably actually do so.