From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46706) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dcJnC-0001Ph-CX for guix-patches@gnu.org; Mon, 31 Jul 2017 19:08:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dcJn8-00062i-BV for guix-patches@gnu.org; Mon, 31 Jul 2017 19:08:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:33189) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dcJn8-00062e-7x for guix-patches@gnu.org; Mon, 31 Jul 2017 19:08:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dcJn7-0000c5-VY for guix-patches@gnu.org; Mon, 31 Jul 2017 19:08:01 -0400 Subject: [bug#27888] [PATCH 01/18] gnu: python@3: Update to 3.6.2. Resent-Message-ID: Date: Mon, 31 Jul 2017 19:07:00 -0400 From: Leo Famulari Message-ID: <20170731230700.GB11946@jasmine.lan> References: <20170731200735.28019-1-mbakke@fastmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="IrhDeMKUP4DT/M7F" Content-Disposition: inline In-Reply-To: <20170731200735.28019-1-mbakke@fastmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Marius Bakke Cc: 27888@debbugs.gnu.org --IrhDeMKUP4DT/M7F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 31, 2017 at 10:07:18PM +0200, Marius Bakke wrote: > * gnu/packages/patches/python-3.5-fix-tests.patch: Rename to ... > * gnu/packages/patches/python-3-fix-tests.patch: ... this. Adjust and disable > more tests. > * gnu/packages/patches/python-3.5-getentropy-on-old-kernels.patch: Delete file. I'm curious, do you know if they handled this issue upstream in a reliable way, or is getentropy() simply unused in Python 3.6? Also, do you have any idea about the state of the bytecode timestamp issue, which is related to the problem with the bytecode cache? I can work on that on python-updates when you push it. --IrhDeMKUP4DT/M7F Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAll/uBMACgkQJkb6MLrK fwjEmg//RkxYYCw/DOwRl6mkK9W7q8Ma7ylZIXQtC2Mn70W/Fk4AWpsAg4RHqXT4 hu876SRSLqLTq15wqjwbN5VOY0WeFHoNTN/XNIQEnp5gKZ1nUg5xtdckUbz8D8qf ++ZHD/zQ79dKAD7FdTMQCCibwkaLETO7dDXRxdKDJMpsfw0q3ZFOWvo9KAPZxRI1 QArgvVs6u3v9uAeAPnRbMt1Q5ZnJtAlqQdLQaWJfqkD6nCBFXe6y08rIHBYHREDc QCnakQwX4qtyWjuFlLQ2tAXAaHvGEj0hi8zBpiUNQWxiF2XjGR2WLT0HkHeIebyg QR/GVEFjHZkbWBvnnuyb0KQGGEHqVLK9FqS5N6p02DaTO3hKHOh4G4YjJkAaR+UQ 0fAfXcn1oPTXJmOGVjpbHdgzosBFB3M+YchHLhc8FVQdvCEC7Y5dGfVQCW9kCw2M TIV1kQBVmwK2OKRqmwyl9/4bHOe4gakTU36ORzQALksqrTzzTHmozXyyCT3fbuwE NlxnDVe8sztnAW458ow02cejZU0rKncT5Xsqt+xCqnoJXrxe7hb6dnqPQUX2AVlP YTytKg7TvPdcfeK76735G3bOkzRkaSNa03AvMslF9QFgwP29bLRmJSLUSCQyH1OS sfbsDhyArhE0gp1PEfDhnSXIyzDxIjqQ+Sjd/iMWylUU3dPB2XM= =Z9Xz -----END PGP SIGNATURE----- --IrhDeMKUP4DT/M7F--