From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org,
David Malcolm <dmalcolm@redhat.com>
Subject: Re: [RFA] ignore PYTHONHOME environment variable.
Date: Tue, 23 Nov 2010 16:31:00 -0000 [thread overview]
Message-ID: <20101123163045.GA1737@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <AANLkTiko2FVL+ktF9JTBRedYz_wvsq_eP4rU3rLcOYmF@mail.gmail.com>
On Tue, 23 Nov 2010 10:29:05 +0100, Doug Evans wrote:
> On Mon, Nov 22, 2010 at 7:00 PM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> > I am not a Python expect but I believe for GDB linked with the only regular
> > system Python $PYTHONHOME should work, even for GDB-Python.
[...]
> I'm not sure I understand the objection.
> AIUI, if gdb is linked with the system python then Joel's patch is
> essentially a nop
> (i.e. PYTHONHOME=/usr would still work).
But PYTHONHOME=$HOME for some user overrides of system Python would no longer
work. What would $PYTHONHOME otherwise be useful for?
At least for $PERL5LIB I add $HOME{/share,/lib{,64}}/perl5 myself. It seems
to me $PERL5LIB is in part $PYTHONHOME (.so) and $PYTHONPATH (.py).
[RFA] ignore PYTHONHOME environment variable.
http://sourceware.org/ml/gdb-patches/2010-11/msg00328.html
Regards,
Jan
next prev parent reply other threads:[~2010-11-23 16:31 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 [this message]
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
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=20101123163045.GA1737@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=dmalcolm@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