Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Paul Koning <paulkoning@comcast.net>
Cc: Kevin Buettner <kevinb@redhat.com>,
	 "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Proposal: Drop GDB support for Python versions < 2.6
Date: Thu, 21 Feb 2019 17:11:00 -0000	[thread overview]
Message-ID: <871s41jced.fsf@tromey.com> (raw)
In-Reply-To: <3A227E41-CC9A-43FF-A526-81FD325215E1@comcast.net> (Paul Koning's	message of "Wed, 20 Feb 2019 17:06:06 -0500")

>>>>> "Paul" == Paul Koning <paulkoning@comcast.net> writes:

Paul> Along the same lines, do you want to drop support for <= 3.x for
Paul> some x?  Python 3 is up to 3.7 now; I'm not sure if it matters
Paul> much to the code or maintenance burden, but dropping support for
Paul> some of the older 3.x releases might also make sense.

I looked and there aren't any major compatibility hacks to handle
different minor versions of Python 3.  It's all stuff along these lines,
and not many instances:

    #if PY_MAJOR_VERSION == 3 && PY_MINOR_VERSION >= 4
                            const char *prompt)
    #else
                            char *prompt)
    #endif

So while I think it would be fine to drop some of this, there doesn't
seem to be a big benefit to doing so.

Tom


  reply	other threads:[~2019-02-21 17:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 20:45 Kevin Buettner
2019-02-20 21:30 ` Paul Smith
2019-02-20 21:44   ` Jan Vrany
2019-02-20 21:49     ` Joel Sherrill
2019-02-20 22:05     ` Paul Smith
2019-02-20 22:11     ` Kevin Buettner
2019-02-20 23:26       ` André Pönitz
2019-02-21  6:39         ` Kevin Buettner
2019-02-21 14:40           ` Eli Zaretskii
2019-02-21 18:35           ` André Pönitz
2019-02-21 18:52             ` John Baldwin
2019-02-21  9:10         ` Dmitry Samersoff
2019-02-20 22:06   ` Paul Koning
2019-02-21 17:11     ` Tom Tromey [this message]
2019-02-20 22:58   ` André Pönitz
2019-02-21  2:39   ` Joel Brobecker
2019-02-21  3:46     ` Eli Zaretskii
2019-02-21  6:46       ` Kevin Buettner
2019-02-21 14:42         ` Eli Zaretskii
2019-02-21 10:45     ` Mark Wielaard
2019-02-21  3:40   ` Eli Zaretskii
2019-02-21 17:55 ` Pedro Alves

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=871s41jced.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb@sourceware.org \
    --cc=kevinb@redhat.com \
    --cc=paulkoning@comcast.net \
    /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