unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: jgart <jgart@dismail.de>, 56243@debbugs.gnu.org
Subject: [bug#56243] [PATCH] gnu: python-debug: Improve description and synopsis.
Date: Mon, 27 Jun 2022 00:40:34 +0200	[thread overview]
Message-ID: <19be37371b7a8e551cad80d45aa839e811f9c542.camel@telenet.be> (raw)
In-Reply-To: <20220626220938.12896-1-jgart@dismail.de>

[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]

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?

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-06-26 22:41 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 [this message]
2022-07-16  3:54   ` bug#56243: " Maxim Cournoyer
2022-07-16  4:04     ` [bug#56243] " 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=19be37371b7a8e551cad80d45aa839e811f9c542.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=56243@debbugs.gnu.org \
    --cc=jgart@dismail.de \
    /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).