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: Tom Tromey <tromey at redhat dot com>
- To: Joel Brobecker <brobecker at adacore 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 08:12:24 -0700
- 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>
>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:
>> I think we could drop Python 2.4 and 2.5 for gdb 7.8. My understanding
>> is that we (Red Hat) won't need support for these in future gdb
>> releases.
Joel> Do we need to keep 2.6? Python 2.7 was released July 3rd 2010, so over
Joel> 3 years ago. GDB 7.8 would probably be around mid summer 2014, so 4 years
Joel> after Python 2.7 got released.
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 --
It seems likely that other groups will also want 2.6 support.
My recollection is that the compatibility difficulties have been with
Python 2.4 and that 2.6 hasn't presented any particular problems.
Looking at the code I see some C hacks for 2.4 and one minor for 2.6.
I'm actually not too concerned about these workarounds, the one that has
been more of a pain is that 2.4 and 2.5 don't have support for the "as"
clause to "except".
thanks,
Tom