From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: Re: Multiple python-3 packages Date: Fri, 27 Jan 2017 18:34:56 +0100 Message-ID: <87bmus2ypr.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> References: <20170127101225.GA28495@jasmine> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60310) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cXAQV-000654-Sb for guix-devel@gnu.org; Fri, 27 Jan 2017 12:35:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cXAQR-0004DM-VW for guix-devel@gnu.org; Fri, 27 Jan 2017 12:35:07 -0500 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:49580) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cXAQR-0004Au-MP for guix-devel@gnu.org; Fri, 27 Jan 2017 12:35:03 -0500 In-Reply-To: <20170127101225.GA28495@jasmine> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Leo Famulari , guix-devel@gnu.org --=-=-= Content-Type: text/plain Leo Famulari writes: > Currently we have Python 3.4 and 3.5. Python 3.6 was released recently. > > When we added 3.5, I thought it was a good idea to keep 3.4 around in > case some packages need it. It turns out that nothing is using it in our > tree. > > Do we want to keep 3.4 and 3.5 around? There is a maintenance cost > incurred at each new release, because their shared patches tend to > diverge each time. > > If we should keep them, how should the package inheritance go? Now, it's > like this: > > 2.7 < 3.5 < 3.4 > > If we kept them all, should 3.5 and 3.4 both inherit 3.6? Hi Leo! I think python 3.x releases should inherit from the latest indeed. That way changes to lower 3.x releases are guaranteed not to affect the newest one. No preference for keeping older releases around either. Unless any python folks wants to maintain them, I think they can be dropped. Perhaps we can use python-3.6 as the basis for a new "python-updates" branch? --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAliLhMAACgkQoqBt8qM6 VPrMfQgAjwvWakGU/MQ7OqWrx4T/HGOdiijR6nOm8rce9+ErnbsOfatwb3fBvbcI zGXxGuFEA7h56jqV8medE3/hnHadRi85co2aFVIGgvlgPi5bLAu2O2svDAeHVSoT BbluA1gahaS4/IzC/xdDfZFXjAF3RDmst1rWsWp/cXLahyLtSrYiOsWNLDoyRA88 kbEOPfoSjWWUtTZCi3xvNxuFsTgeYsrRiQB5z2RmkXvyzvVvlfo1eTDPj5TjFrYy CdUsRC25E7faFu0vKzj1CJghFDkUoOAma4e9XbRbaJzNV++0rnv3UNMxTq5fkp29 Rm2gII4TfmqRh+RHOjbPGpe9mLbFWw== =OdSS -----END PGP SIGNATURE----- --=-=-=--