Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.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:12:00 -0000	[thread overview]
Message-ID: <87zjo72zhj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20131211075328.GA3227@adacore.com> (Joel Brobecker's message of	"Wed, 11 Dec 2013 08:53:28 +0100")

>>>>> "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


  parent reply	other threads:[~2013-12-11 15:12 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 [this message]
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

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=87zjo72zhj.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jkratoch@redhat.com \
    --cc=sergiodj@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