From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Restarting 'python-updates' Date: Fri, 23 Jun 2017 14:07:52 -0400 Message-ID: <20170623180752.GA11691@jasmine.lan> References: <87r2yaoe4m.fsf@fastmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="nFreZHaLTZJo0R7j" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34848) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dOSzv-00022U-RA for guix-devel@gnu.org; Fri, 23 Jun 2017 14:08:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dOSzs-0003qA-Ko for guix-devel@gnu.org; Fri, 23 Jun 2017 14:07:59 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:39913) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dOSzs-0003pY-9m for guix-devel@gnu.org; Fri, 23 Jun 2017 14:07:56 -0400 Content-Disposition: inline In-Reply-To: <87r2yaoe4m.fsf@fastmail.com> 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: Marius Bakke Cc: guix-devel@gnu.org --nFreZHaLTZJo0R7j Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 23, 2017 at 06:36:09PM +0200, Marius Bakke wrote: > Python 3.6.2 is scheduled to be released in about a week[0]. >=20 > Our current Python 3.5 is EOL[1], so we should upgrade ASAP. 3.6.2 seems > like a good excuse. It would be good to start building a branch based on > it once it is released (or core-updates is merged, whichever is last). We could also start sooner with Python 3.6.1, if people are eager to begin working :) > Are there any objections to deleting the current 'python-updates' branch > and starting a fresh one? Looking at `git log master..python-updates`, > most of the commits seem to have made their way to 'master' in some form. No objections! > I would also like to try making the newer versions of 'pytest' and > 'mock' the default and instead add lower versions as necessary. Would > that be too much for one cycle? >=20 > Updating the heavy-impact python libraries will require upgrading many > collateral packages and solving new dependency cycles, so I'm hoping we > can start this effort earlier to make the process smoother. Thoughts? It will be quite a bit of work to upgrade the "core" Python libraries, but we have to do it. Your suggestion to reverse the "default" versions is a good one. I thought this Nix proposal to treat Python tests as their own derivations is an interesting idea for cutting the Gordian knot of Python dependency cycles: https://github.com/NixOS/nixpkgs/issues/26400 But, I don't mind if we skip this for now. It depends on peoples' motivation. However, I want to fix the bytecode caching issue in this cycle. It's a bad performance bug :( https://github.com/NixOS/nixpkgs/issues/22569 --nFreZHaLTZJo0R7j Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAllNWPAACgkQJkb6MLrK fwhnpg/9F1O9KcX/n6qBhODkMtGMuh8Z0Bvvnqvju6TKetnjKJkvEvWhPMSWPlUz nVdzwfarAQbLd2w0Opbip9C/VFGhyZqzjeKsx0pUYiPm3Mo4ocxusX/JHQ6stsyf eg6rnpOQodlZ748qEzjMZDA5JQ0k+J08uywins4Tu3OyOoiP3CfhyMgKuYD+eGpW VbAyQ0cw87oMZFzGd43RXewWO5qM3oIi/lGIi7RE4ZWcuzdvJHakLItNQQYNvXw5 9rVchvqItjaPohODNGZkvEin/nD29pDrQAGaw2LdrcubdjyPmC1KbUj2BmOUf1DG KO5UI5S26UEn6QEJTWQxuM+KSLnKCLZnwpbrsduR7lvVi0oq+JIk9UkGaiCVZbwH 7mtCzqJxPi2fREMzW/ZAQSleDhyJu1y4iDdgLsUVq2GR/+AZm0cKgin7m+5aN6pH YDR2zQmqKN5oBZHAzzEBKhENZl/TcRaxeUjFgbG0cQKUxbgTZaBNKt9gXlN9ValX SGCTCTxeMbzw0LFucQlVnc8U55Bc/Xg1YEhcbtfSNjPDGhVkZtK2IMNlC/AsrXbq kuG6HIT2iKE5TmxYyZ/Dk7JMnvYlQwpIbfY0iVIG2aG9LwaNDwH3iUP0tHZHvGen y+Pv6lhlpd7zgJVXPeFc8lU+8QiigcUVsiN5K3sV7hPfEVcjD6E= =Q8aD -----END PGP SIGNATURE----- --nFreZHaLTZJo0R7j--