From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] set/show python dont-write-bytecode fixes
Date: Mon, 25 Jul 2022 12:07:25 -0700 [thread overview]
Message-ID: <20220725120725.0294785f@f35-zws-1> (raw)
In-Reply-To: <aef9d06d-312a-7485-c7eb-efcc3c6b6fd8@simark.ca>
On Sun, 24 Jul 2022 21:04:58 -0400
Simon Marchi <simark@simark.ca> wrote:
> On 2022-07-23 17:23, Kevin Buettner wrote:
> >
> > -By default this option is set to @samp{auto}, in this mode Python will
> > -check the environment variable @env{PYTHONDONTWRITEBYTECODE} to see
> > -if it should write out byte-code or not.
> > +By default this option is set to @samp{auto}. In this mode, provided
> > +the @code{python ignore-environment} setting is @samp{off}, the
> > +environment variable @env{PYTHONDONTWRITEBYTECODE} is examined to see
> > +if it should write out byte-code or not.
>
> Spurious space at the end of this line. Otherwise, LGTM.
Fixed and pushed.
Kevin
prev parent reply other threads:[~2022-07-25 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 21:23 Kevin Buettner
2022-07-24 5:40 ` Eli Zaretskii
2022-07-25 1:04 ` Simon Marchi
2022-07-25 19:07 ` Kevin Buettner [this message]
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=20220725120725.0294785f@f35-zws-1 \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.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.
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).