public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 1/2] gdb/python: remove Python 2 support
Date: Mon, 21 Mar 2022 16:58:26 +0200	[thread overview]
Message-ID: <83lex3fj3h.fsf@gnu.org> (raw)
In-Reply-To: <20220321144624.1450968-2-simon.marchi@efficios.com> (message from Simon Marchi via Gdb-patches on Mon, 21 Mar 2022 10:46:23 -0400)

> Date: Mon, 21 Mar 2022 10:46:23 -0400
> From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
> 
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 4308e170e41..32d7ae0dd1f 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -3,6 +3,9 @@
>  
>  *** Changes since GDB 12
>  
> +* Remove support for building against Python 2, it is now only possible to
> +* build GDB against Python 3.
> +
>  *** Changes in GDB 12

This part is OK.

> diff --git a/gdb/doc/python.texi b/gdb/doc/python.texi
> index 918418b08c9..a401615e898 100644
> --- a/gdb/doc/python.texi
> +++ b/gdb/doc/python.texi
> @@ -18,8 +18,7 @@
>  You can extend @value{GDBN} using the @uref{http://www.python.org/,
>  Python programming language}.  This feature is available only if
>  @value{GDBN} was configured using @option{--with-python}.
> -@value{GDBN} can be built against either Python 2 or Python 3; which
> -one you have depends on this configure-time option.
> +@value{GDBN} can be built against Python 3.

Here, I think we should say "only against Python 3", or say "Python 2
is not supported as of GDB 13", or something to that effect.  Because
it is otherwise strange to mention Python 3, it sounds "out of the
blue".

Thanks.

  parent reply	other threads:[~2022-03-21 14:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07 15:29 [PATCH 1/3] " Simon Marchi
2022-01-07 15:29 ` [PATCH 2/3] gdb/python: remove Python 2/3 compatibility macros Simon Marchi
2022-01-07 15:29 ` [PATCH 3/3] gdb/python: drop support for Python < 3.4 Simon Marchi
2022-01-07 16:33   ` Eli Zaretskii
2022-01-07 17:14     ` Simon Marchi
2022-01-07 15:33 ` [PATCH 1/3] gdb/python: remove Python 2 support Paul Koning
2022-01-07 15:41   ` Simon Marchi
2022-01-07 17:44 ` Andrew Burgess
2022-01-08  8:18   ` Joel Brobecker
2022-01-10  2:28     ` Simon Marchi
2022-01-10  2:59       ` Joel Brobecker
2022-01-10 16:39         ` Simon Marchi
2022-01-11  3:26           ` Joel Brobecker
2022-01-10 16:26       ` Tom Tromey
2022-03-03 16:31 ` Andrew Burgess
2022-03-03 17:40   ` Simon Marchi
2022-03-21 14:46 ` [PATCH v2 0/2] Remove " Simon Marchi
2022-03-21 14:46   ` [PATCH v2 1/2] gdb/python: remove " Simon Marchi
2022-03-21 14:50     ` Simon Marchi
2022-03-21 14:58     ` Eli Zaretskii [this message]
2022-03-21 15:04       ` Simon Marchi
2022-03-21 15:33         ` Pedro Alves
2022-03-21 16:31           ` Simon Marchi
2022-03-21 16:55             ` Pedro Alves
2022-03-21 17:04               ` Simon Marchi
2022-03-21 14:46   ` [PATCH v2 2/2] gdb/python: remove Python 2/3 compatibility macros Simon Marchi
2022-03-23 11:46   ` [PATCH v2 0/2] Remove Python 2 support Simon Marchi

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=83lex3fj3h.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@efficios.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).