From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Status update on reproducible builds in Guix
Date: Mon, 6 Nov 2017 11:19:18 +0100 [thread overview]
Message-ID: <88b0ebb2-3bed-adbd-7348-51940f1607b9@crazy-compilers.com> (raw)
In-Reply-To: <87ineneql0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
Am 06.11.2017 um 09:52 schrieb Ludovic Courtès:
>> [15:37:41] <mb[m]1> At this stage we might as well wait for this to land
>> upstream: https://www.python.org/dev/peps/pep-0552/
>>
>> So, it seems, that we are waiting for this pep to land upstream.
> Cool, thanks for the notification.
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.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
[-- Attachment #2: Type: text/html, Size: 1656 bytes --]
next prev parent reply other threads:[~2017-11-06 10:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 10:33 Status update on reproducible builds in Guix Ludovic Courtès
2017-11-01 6:22 ` Jan Nieuwenhuizen
2017-11-05 15:49 ` Ludovic Courtès
2017-11-05 19:04 ` Gábor Boskovits
2017-11-05 19:16 ` Hartmut Goebel
2017-11-05 19:17 ` ng0
2017-11-06 8:52 ` Ludovic Courtès
2017-11-06 10:19 ` Hartmut Goebel [this message]
2017-11-06 11:47 ` Gábor Boskovits
2017-11-07 9:55 ` Eric Myhre
2017-11-07 10:12 ` Hartmut Goebel
2017-11-06 21:29 ` Marius Bakke
2017-11-07 9:16 ` Hartmut Goebel
2017-11-07 19:00 ` Marius Bakke
2017-11-06 21:14 ` Marius Bakke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88b0ebb2-3bed-adbd-7348-51940f1607b9@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.