From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40865) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dcL5V-0002Ik-Vo for guix-patches@gnu.org; Mon, 31 Jul 2017 20:31:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dcL5S-0001rn-Rs for guix-patches@gnu.org; Mon, 31 Jul 2017 20:31:05 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:33237) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dcL5S-0001ra-KK for guix-patches@gnu.org; Mon, 31 Jul 2017 20:31:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1dcL5S-0002Vk-Bi for guix-patches@gnu.org; Mon, 31 Jul 2017 20:31:02 -0400 Subject: [bug#27888] [PATCH 01/18] gnu: python@3: Update to 3.6.2. Resent-Message-ID: From: Marius Bakke In-Reply-To: <20170731230700.GB11946@jasmine.lan> References: <20170731200735.28019-1-mbakke@fastmail.com> <20170731230700.GB11946@jasmine.lan> Date: Tue, 01 Aug 2017 02:30:34 +0200 Message-ID: <87zibkw2mt.fsf@fastmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" 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: Leo Famulari Cc: 27888@debbugs.gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Leo Famulari writes: > 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 di= sable >> more tests. >> * gnu/packages/patches/python-3.5-getentropy-on-old-kernels.patch: Delet= e 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? The getentropy fix for 3.5 was a port of "random.c" from 3.6 + the fix % 3.5 specific behaviour. Since 3.6.2 was just released it should have it. Most hunks are there, but didn't verify all. > 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. Yes. You might have seen this: https://github.com/NixOS/nixpkgs/pull/25916 NixOS patches the interpreter to unconditionally set bytecode timestamps to epoch 1. Now I also found this: https://github.com/python/cpython/pull/296 So I think we only need that patch and to set PYTHONHASHSEED to some deterministic value in python-build-system.=20 I can give it a go next weekend if you're busy, but more than happy to share the workload :-) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAll/y6sACgkQoqBt8qM6 VPpd5QgAlgkwuuOH4JzrrKpUHaaFVAN6ibHfcdCjidFvEFa8WrsHFLdW/fF1NnyI KspIj+LUMmsmL+M5pyLaSzQ+A0i7f2c949e/BV8AfkccDfib80h8UtvHobssm+ZU RhMPk2XS4HIN94f4xz6vKuplLg/A3Ywddf/SVmcsua2Pdm3MyG2IwiQhz/kLayZ0 RGcMQ1rzsUKhpBDW2Pi83vj4LY7Nur1At9/Xot672jIQ1bnQCLaJrNDAGnuFcomi 64AcZ9BdqfxsOfPf1f1Yjf88jZ+yak3aG51oIfeRLFaLtLpvUT2JJXCXTsTqSc4X TqChpFb2Did4dnW5+jNRa2MErfuDYQ== =d9jM -----END PGP SIGNATURE----- --=-=-=--