From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 56243-done@debbugs.gnu.org, jgart <jgart@dismail.de>
Subject: bug#56243: [PATCH] gnu: python-debug: Improve description and synopsis.
Date: Fri, 15 Jul 2022 23:54:25 -0400 [thread overview]
Message-ID: <87ilnxr9u6.fsf_-_@gmail.com> (raw)
In-Reply-To: <19be37371b7a8e551cad80d45aa839e811f9c542.camel@telenet.be> (Maxime Devos's message of "Mon, 27 Jun 2022 00:40:34 +0200")
Hi,
Maxime Devos <maximedevos@telenet.be> writes:
> jgart via Guix-patches via schreef op zo 26-06-2022 om 17:09 [-0500]:
>> (synopsis
>> - "High-level, dynamically-typed programming language (for debugging)")
>> + "Python with the debug hooks enabled")
>> (description
>> - "This variant of Python provides an interpreter built with
>> -@code{--with-pydebug} to help develop and debug extensions. See
>> +"This variant of Python provides an interpreter
>> +built with the @code{--with-pydebug} flag, enabling
>> +debug hooks for development or testing purposes. See
>> @url{https://pythonextensionpatterns.readthedocs.io/en/latest/debugging/debug.html},
>> for more information.")))
>
> I can't tell whether the old or new description is better but the new
> synopsis seems better to me (more to the point and descriptive -- you
> can do debugging in the regular python too!). Maybe it would be even
> better to make clear in the description that you can also do debugging
> with the _regular_ python package?
I pushed the improved synopsis, but also had doubts about the
description change, so left it out in
15943fa75788edb8d9ed1c3d8d320f50d21e4baa.
Closing.
Thanks,
Maxim
next prev parent reply other threads:[~2022-07-16 3:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-26 22:09 [bug#56243] [PATCH] gnu: python-debug: Improve description and synopsis jgart via Guix-patches via
2022-06-26 22:40 ` Maxime Devos
2022-07-16 3:54 ` Maxim Cournoyer [this message]
2022-07-16 4:04 ` jgart via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilnxr9u6.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=56243-done@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=maximedevos@telenet.be \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).