Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb@sourceware.org
Subject: Proposal: Drop GDB support for Python versions < 2.6
Date: Wed, 20 Feb 2019 20:45:00 -0000	[thread overview]
Message-ID: <20190220134506.13960235@f29-4.lan> (raw)

I want to drop support in GDB for Python versions 2.5 and lower.

I've proposed two patches which use facilities that are only present
in Python 2.6 and later.  To be clear, these mechanisms are also
present in Python 2.7 and 3.X.  Python documentation encourages use of
these newer facilities over the older ones.

My patches can be found here:

https://sourceware.org/ml/gdb-patches/2019-02/msg00311.html

https://sourceware.org/ml/gdb-patches/2019-02/msg00314.html

The latter patch provides a detailed rationale for dropping support
for older versions of Python.  Here is a brief summary:

Python 2.6 was first released in Oct, 2008.  Five years later, in Oct,
2013, a final security release was made along with the announcement
that support for Python 2.6 has ended.  That being the case, it seems
reasonable for GDB to end support for all Python versions prior to
Python 2.6.

Going even further, since 2.6 is no longer supported by the Python
community, I'd also be okay with saying that GDB only supports Python
2.7 and Python 3.X.

Comments?


             reply	other threads:[~2019-02-20 20:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 20:45 Kevin Buettner [this message]
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
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=20190220134506.13960235@f29-4.lan \
    --to=kevinb@redhat.com \
    --cc=gdb@sourceware.org \
    /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