This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Add some const-ness to py-cmd.c
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>, Tom Tromey <tromey at redhat dot com>
- Cc: Doug Evans <xdje42 at gmail dot com>, gdb-patches at sourceware dot org, Sergio Durigan <sergiodj at redhat dot com>, Jan Kratochvil <jkratoch at redhat dot com>
- Date: Wed, 11 Dec 2013 15:57:39 +0000
- Subject: Re: [PATCH] Add some const-ness to py-cmd.c
- Authentication-results: sourceware.org; auth=none
- References: <m3vbyzydik dot fsf at sspiff dot org> <871u1k5srh dot fsf at fleche dot redhat dot com> <87fvq03waa dot fsf at fleche dot redhat dot com> <20131211075328 dot GA3227 at adacore dot com> <87zjo72zhj dot fsf at fleche dot redhat dot com> <20131211153648 dot GB3227 at adacore dot 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