bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>, bug-gnulib@gnu.org
Subject: diffutils __pycache__ failure.
Date: Mon, 22 Apr 2024 01:51:59 -0700	[thread overview]
Message-ID: <06d7214b-1b29-44c2-9e79-ae1e68249691@gmail.com> (raw)
In-Reply-To: <aeef2d18-4e15-4b22-8e23-708234f244af@gmail.com>

On 4/22/24 1:23 AM, Collin Funk wrote:
> It looks like it can be turned off with 'python3 -B' or setting the
> PYTHONDONTWRITEBYTECODE environment variable to a non-empty string [1]
> [2].

I was able to reproduce the issue. Modifying the 'gnulib-tool.py'
shell script in the 'gnulib' submodule so that -B is passed to
'python3' fixes it for me.

Leaving it without a ChangeLog entry for now just incase someone has a
better idea. I have no clue if this has a noticeable performance
impact or not.

diff --git a/gnulib-tool.py b/gnulib-tool.py
index cdcd316909..1d45181014 100755
--- a/gnulib-tool.py
+++ b/gnulib-tool.py
@@ -147,4 +147,4 @@
 profiler_args=
 # For profiling, cf. <https://docs.python.org/3/library/profile.html>.
 #profiler_args="-m cProfile -s tottime"
-exec python3 $profiler_args "$gnulib_dir/.gnulib-tool.py" "$@"
+exec python3 -B $profiler_args "$gnulib_dir/.gnulib-tool.py" "$@"

Collin


  reply	other threads:[~2024-04-22  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-21 10:52 GNU gnulib: calling for beta-testers Bruno Haible
2024-04-21 11:52 ` Vivien Kraus
2024-04-22  7:56 ` Paul Eggert
2024-04-22  8:23   ` Collin Funk
2024-04-22  8:51     ` Collin Funk [this message]
2024-04-22 11:38       ` diffutils __pycache__ failure Bruno Haible
2024-04-22 19:44         ` Collin Funk
2024-04-22 20:55           ` Bruno Haible
2024-04-22 11:22     ` GNU gnulib: calling for beta-testers Bruno Haible
2024-04-22 20:00       ` Collin Funk
2024-04-22 20:56         ` Bruno Haible

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=06d7214b-1b29-44c2-9e79-ae1e68249691@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=bug-gnulib@gnu.org \
    --cc=eggert@cs.ucla.edu \
    /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. 
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).