From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Doug Evans <dje@google.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] ignore PYTHONHOME environment variable.
Date: Mon, 17 Jan 2011 10:36:00 -0000 [thread overview]
Message-ID: <20110115114214.GY2504@adacore.com> (raw)
In-Reply-To: <20110115110917.GA14598@host1.dyn.jankratochvil.net>
On Sat, Jan 15, 2011 at 12:09:17PM +0100, Jan Kratochvil wrote:
> On Sat, 15 Jan 2011 08:55:59 +0100, Doug Evans wrote:
> > if GDB_PYTHONHOME provided
> > use it
> > elseif PYTHONHOME provided
> > use it
> > else
> > use default
> > endif
> >
> > That way a user can provide a PYTHONHOME and gdb will use it. But if
> > it is incompatible with the python that gdb is using, they can still
> > have PYTHONHOME - they just need to set GDB_PYTHONHOME too.
>
> I find this setup fine, Joel had some disagreements with it.
I must have misunderstood, because I don't remember disagreeing to
this proposal. I think that having a GDB_PYTHONHOME is a useful thing
to have, regardless of the disagreement on PYTHONHOME (which, I think,
is an orthogonal matter).
I'd say go for it.
--
Joel
next prev parent reply other threads:[~2011-01-15 11:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 1:03 Joel Brobecker
2010-11-23 3:01 ` Jan Kratochvil
2010-11-23 9:29 ` Doug Evans
2010-11-23 16:31 ` Jan Kratochvil
2010-11-23 16:57 ` Doug Evans
2010-11-23 17:31 ` Joel Brobecker
2010-12-14 7:12 ` Joel Brobecker
2010-12-14 9:27 ` Jan Kratochvil
2010-12-14 10:33 ` Joel Brobecker
2011-01-13 22:57 ` Joel Brobecker
2011-01-15 9:17 ` Doug Evans
2011-01-15 11:26 ` Jan Kratochvil
2011-01-17 10:36 ` Joel Brobecker [this message]
2012-05-18 19:34 ` Jan Kratochvil
2012-05-28 14:41 ` Joel Brobecker
2012-05-28 17:30 ` Jan Kratochvil
2012-05-29 14:54 ` Joel Brobecker
2012-05-29 15:57 ` Jan Kratochvil
2012-05-30 14:37 ` Jan Kratochvil
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=20110115114214.GY2504@adacore.com \
--to=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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