From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Eric Myhre" <hash@exultant.us>, "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Status update on reproducible builds in Guix
Date: Tue, 7 Nov 2017 11:12:55 +0100 [thread overview]
Message-ID: <0f55d972-124b-3a36-e9c2-e943b6b5755a@crazy-compilers.com> (raw)
In-Reply-To: <807414F1-6A4B-46ED-9822-ADF2142B3DDB@exultant.us>
Am 07.11.2017 um 10:55 schrieb Eric Myhre:
> 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.
This env-var disables byt-code caching (.pyc files), thus every module
needs to be recompiled every time is is used.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2017-11-07 10:16 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
2017-11-07 10:12 ` Hartmut Goebel [this message]
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=0f55d972-124b-3a36-e9c2-e943b6b5755a@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=hash@exultant.us \
/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).