From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hartmut Goebel Subject: Re: Status update on reproducible builds in Guix Date: Tue, 7 Nov 2017 10:16:14 +0100 Message-ID: <99f8f4af-fa48-7300-8db3-cb64a30233a2@crazy-compilers.com> References: <87bmknzjx1.fsf@gnu.org> <87y3nqwmb7.fsf@gnu.org> <87efpcsp3m.fsf@gnu.org> <87ineneql0.fsf@gnu.org> <88b0ebb2-3bed-adbd-7348-51940f1607b9@crazy-compilers.com> <87bmkf3xkb.fsf@fastmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="------------F977CB30848B4147A1C343C7" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59441) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eBzzo-0007gR-HF for guix-devel@gnu.org; Tue, 07 Nov 2017 04:16:37 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eBzzi-0001cV-Fy for guix-devel@gnu.org; Tue, 07 Nov 2017 04:16:36 -0500 In-Reply-To: <87bmkf3xkb.fsf@fastmail.com> Content-Language: en-US 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 , =?UTF-8?Q?Ludovic_Court=c3=a8s?= , =?UTF-8?Q?G=c3=a1bor_Boskovits?= Cc: Guix-devel This is a multi-part message in MIME format. --------------F977CB30848B4147A1C343C7 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Am 06.11.2017 um 22:29 schrieb Marius Bakke: >> Seems like my message did not go through: >> >> This change will not solve out problem! >> >> PEP 552 proposes a new file-format for .pyc file and a hash-based >> mechanism for checking if the .pyc file is recent. This means, you can= >> not backport this changes to Python 3.6 or older. Even if you manage t= o >> backport, this would seriously break all tools working on .pyc files. > We only support Python 2 and the latest (in Guix, anyway!) Python 3 > interpreter. So while we will indeed need a solution for Python2, we > don't have to care about older 3.x variants. This depends on what you call "older 3.5 variants". :-) The current version is Python 3.6. Guix has 3.5 (and 2.7). Python 3.7 (which will materialize PEP 552 ) is planed for mid of 2018. --=20 Regards Hartmut Goebel | Hartmut Goebel | h.goebel@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible | --------------F977CB30848B4147A1C343C7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Am 06.11.2017 um 22:29 schrieb Marius Bakke:
Seems like my message did not go through:

This change will not solve out problem!

PEP 552 proposes a new file-format for .pyc file and a hash-based
mechanism for checking if the .pyc file is recent. This means, you can
not backport this changes to Python 3.6 or older. Even if you manage to
backport, this would seriously break all tools working on .pyc files.

We only support Python 2 and the latest (in Guix, an=
yway!) Python 3
interpreter.  So while we will indeed need a solution for Python2, we
don't have to care about older 3.x variants.

This depends on what you call "older 3.5 variants". :-)

The current version is Python 3.6. Guix has 3.5 (and 2.7).

Python 3.7 (which will materialize PEP 552 ) is planed for mid of 2018.

--=20
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com   =
            |
| www.crazy-compilers.com | compilers which you thought are impo=
ssible |
--------------F977CB30848B4147A1C343C7--