From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tom@tromey.com>, Simon Marchi <simon.marchi@polymtl.ca>
Cc: Orgad Shaneh <orgads@gmail.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix python compatibility with old versions of GDB
Date: Tue, 13 Jun 2017 12:29:00 -0000 [thread overview]
Message-ID: <f90b37fd-8964-22e1-6851-8dc0eb665b62@redhat.com> (raw)
In-Reply-To: <87o9tsozn6.fsf@pokyo>
On 13/06/17 13:11, Tom Tromey wrote:
>>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
>
>>> Practically the data-directory is mostly backwards-compatible, except
>>> this small part which I found (there might be others which I didn't
>>> find). With this patch, I'm able to run GDB 7.8 with the latest
>>> data-directory.
>
>>> Is there a reason not to accept it?
>
> Simon> I'd like to know what other maintainers think about this. We may have
> Simon> already faced this situation before and taken a decision which I'm not
> Simon> aware of. Otherwise, we need to take it now.
>
> I think it doesn't make sense to have a policy allowing the sharing of
> installed Python scripts across versions. If this were a policy then it
> would mean that the scripts could never use new features of gdb's Python
> layer -- but that's clearly an absurd result.
I agree. It would make maintenance a nightmare, moreso with supporting Python 2 and 3.
Cheers
Phil
next prev parent reply other threads:[~2017-06-13 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 17:48 Orgad Shaneh
2017-06-11 21:09 ` Simon Marchi
2017-06-12 4:31 ` Orgad Shaneh
2017-06-13 11:23 ` Simon Marchi
2017-06-13 12:12 ` Tom Tromey
2017-06-13 12:29 ` Phil Muldoon [this message]
2017-06-13 14:44 ` Eli Zaretskii
2017-06-13 17:29 ` Simon Marchi
2017-06-13 17:47 ` Matt Rice
2017-06-13 18:42 ` Tom Tromey
2017-06-13 19:33 ` Eli Zaretskii
2017-06-13 19:30 ` Eli Zaretskii
2017-06-13 12:53 ` Paul.Koning
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=f90b37fd-8964-22e1-6851-8dc0eb665b62@redhat.com \
--to=pmuldoon@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=orgads@gmail.com \
--cc=simon.marchi@polymtl.ca \
--cc=tom@tromey.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