From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Marco Barisione <mbarisione@undo.io>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/docs: add parentheses in Python examples using print
Date: Fri, 08 Jan 2021 12:22:59 +0200 [thread overview]
Message-ID: <83h7nrk9rw.fsf@gnu.org> (raw)
In-Reply-To: <20210108092935.92106-1-mbarisione@undo.io> (message from Marco Barisione via Gdb-patches on Fri, 8 Jan 2021 09:29:35 +0000)
> Date: Fri, 8 Jan 2021 09:29:35 +0000
> From: Marco Barisione via Gdb-patches <gdb-patches@sourceware.org>
>
> This makes the examples work both in Python 2 and 3.
>
> gdb/doc/ChangeLog:
>
> * python.texi: Add parentheses to print statements/functions.
I'm okay with the changes, assuming that some Python person says it's
indeed correct from Python POV.
Thanks.
next prev parent reply other threads:[~2021-01-08 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-08 9:29 Marco Barisione via Gdb-patches
2021-01-08 10:22 ` Eli Zaretskii via Gdb-patches [this message]
2021-01-08 14:04 ` Andrew Burgess
2021-01-25 14:07 ` [PING][PATCH] " Marco Barisione via Gdb-patches
2021-01-25 15:30 ` Simon Marchi via Gdb-patches
2021-01-25 15:41 ` Eli Zaretskii via Gdb-patches
2021-01-25 15:50 ` Marco Barisione via Gdb-patches
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=83h7nrk9rw.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=eliz@gnu.org \
--cc=mbarisione@undo.io \
/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