From: Phil Muldoon <pmuldoon@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>, Tom Tromey <tromey@redhat.com>
Cc: Doug Evans <xdje42@gmail.com>,
gdb-patches@sourceware.org,
Sergio Durigan <sergiodj@redhat.com>,
Jan Kratochvil <jkratoch@redhat.com>
Subject: Re: [PATCH] Add some const-ness to py-cmd.c
Date: Wed, 11 Dec 2013 15:57:00 -0000 [thread overview]
Message-ID: <52A88B73.5000503@redhat.com> (raw)
In-Reply-To: <20131211153648.GB3227@adacore.com>
On 11/12/13 15:36, Joel Brobecker wrote:
>> Red Hat at least needs 2.6 for a while still. RHEL 6 ships Python 2.6.
>> It would be more convenient for us if this were supported by gdb.
>>
>> Of course gdb can go its own route and we will cope somehow.
>> A few points though --
>
> Just to be clear, I have no objection whatsoever towards keeping
> support for 2.6! I don't think it is going to be that much more
> work in any case, but just wondered whether that was necessary.
> The one transition that worries me is 3.x, and I think this one
> is going to hurt (at AdaCore).
FWIW, GDB is ready to go with Python 3.x. I check the builds weekly
against the test-suite. There may still be some logic bugs hiding
(like a recent one I fixed: Python 3.x's internal representation of
integers changed to be longs only; that caused an out of order logic
bug in Python conversion routines in GDB which has to support 2.x and
3.x.) So your GDB pain, at least, should be mitigated ;)
Cheers,
Phil
prev parent reply other threads:[~2013-12-11 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-08 8:05 Doug Evans
2013-12-09 10:39 ` Phil Muldoon
2013-12-10 20:57 ` Tom Tromey
2013-12-11 3:24 ` Tom Tromey
2013-12-11 7:53 ` Joel Brobecker
2013-12-11 8:11 ` Jan Kratochvil
2013-12-11 15:12 ` Tom Tromey
2013-12-11 15:36 ` Joel Brobecker
2013-12-11 15:43 ` Tom Tromey
2013-12-11 15:56 ` Joel Brobecker
2013-12-11 15:57 ` Phil Muldoon [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=52A88B73.5000503@redhat.com \
--to=pmuldoon@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jkratoch@redhat.com \
--cc=sergiodj@redhat.com \
--cc=tromey@redhat.com \
--cc=xdje42@gmail.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