From: Doug Evans <dje@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
Meador Inge <meadori@codesourcery.com>,
gdb@sourceware.org
Subject: Re: Using Py_SetPythonHome
Date: Tue, 18 Sep 2012 19:38:00 -0000 [thread overview]
Message-ID: <CADPb22R4cTRqHyRi6asd6muJooPFPaCaRi2DDuqEtA+ew9jrRQ@mail.gmail.com> (raw)
In-Reply-To: <20120917174611.GA27891@host2.jankratochvil.net>
On Mon, Sep 17, 2012 at 10:46 AM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Mon, 17 Sep 2012 19:06:57 +0200, Joel Brobecker wrote:
>> I believe Jan contacted the Python developers, and their answer
>> seemed to go in Jan's direction.
>
> Sorry for not replying it myself.
>
> The thread mails in each month:
> [RFA] ignore PYTHONHOME environment variable.
> http://sourceware.org/ml/gdb-patches/2010-11/msg00328.html
> http://sourceware.org/ml/gdb-patches/2010-12/msg00214.html
> http://sourceware.org/ml/gdb-patches/2011-01/msg00307.html
> http://sourceware.org/ml/gdb-patches/2012-05/msg00710.html
>
> and the last one with Python upstream decision:
> http://sourceware.org/ml/gdb-patches/2012-05/msg01041.html
It's not clear to me that upstream has made a decision (or that they
sufficiently understand our use-case).
btw, for reference sake, I'm not opposed to [1].
http://sources.redhat.com/ml/gdb-patches/2010-11/msg00328.html
If we need to provide some flexibility (via GDB_PYTHONHOME or some
command-line option) we could do so later when the need is justified.
next prev parent reply other threads:[~2012-09-18 19:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 23:23 Meador Inge
2012-09-17 17:07 ` Joel Brobecker
2012-09-17 17:46 ` Jan Kratochvil
2012-09-18 19:38 ` Doug Evans [this message]
2012-09-19 8:04 ` Jan Kratochvil
2012-09-21 15:37 ` Joel Brobecker
2012-09-21 15:44 ` Jan Kratochvil
2012-09-21 15:58 ` Joel Brobecker
2012-09-21 17:28 ` Jan Kratochvil
2012-10-02 13:09 ` Joel Brobecker
2012-10-03 15:13 ` Jan Kratochvil
2012-10-03 15:14 ` Jan Kratochvil
2012-10-03 15:39 ` Joel Brobecker
2012-10-03 17:44 ` Eli Zaretskii
2012-10-03 17:54 ` Jan Kratochvil
2012-10-03 17:57 ` Paul_Koning
2012-10-03 18:35 ` Eli Zaretskii
2012-10-03 18:43 ` Jan Kratochvil
2012-10-03 18:52 ` Eli Zaretskii
2012-10-03 19:03 ` Jan Kratochvil
2012-10-03 19:10 ` Eli Zaretskii
2012-10-03 19:54 ` Paul_Koning
2012-10-03 20:04 ` Jan Kratochvil
2012-10-03 20:11 ` Alfred M. Szmidt
2012-10-03 18:40 ` Eli Zaretskii
2012-10-03 19:26 ` Terekhov, Mikhail
2012-10-04 7:33 ` John Gilmore
2012-10-11 8:42 ` Jan Kratochvil
2012-10-11 14:54 ` Doug Evans
2012-09-21 15:55 ` Meador Inge
2012-09-21 16:01 ` Jan Kratochvil
2012-09-21 16:36 ` Doug Evans
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=CADPb22R4cTRqHyRi6asd6muJooPFPaCaRi2DDuqEtA+ew9jrRQ@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=meadori@codesourcery.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox