unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Myhre <hash@exultant.us>
To: "Gábor Boskovits" <boskovits@gmail.com>,
	"Hartmut Goebel" <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Status update on reproducible builds in Guix
Date: Tue, 07 Nov 2017 10:55:04 +0100	[thread overview]
Message-ID: <807414F1-6A4B-46ED-9822-ADF2142B3DDB@exultant.us> (raw)
In-Reply-To: <CAE4v=piUH2XjWCN7PG74v=_EJWEJeda=+aGnpbNJTD5off8qUQ@mail.gmail.com>

iirc there is even an env var you can set -- PYTHONDONTWRITEBYTECODE=anyvalue -- which will prevent these .pyc files from ever being generated.

There are no ill effects to this I have ever noticed in several years of having it set in my bashrc.

On 6 November 2017 12:47:03 CET, "Gábor Boskovits" <boskovits@gmail.com> wrote:
>
>Regarding message of ng0:
>Debian does not ship pyc files, they compile  them at install time, so
>this
>reproducibility issue does not affect them.
>
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

  reply	other threads:[~2017-11-07  9:55 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
2017-11-06 11:47           ` Gábor Boskovits
2017-11-07  9:55             ` Eric Myhre [this message]
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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=807414F1-6A4B-46ED-9822-ADF2142B3DDB@exultant.us \
    --to=hash@exultant.us \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).