Discrepancy between Python and Guile wrt exiting the interpreter

[Eli Zaretskii]

> From: Pedro Alves <palves@redhat.com>
> Date: Thu, 23 Jan 2020 17:36:28 +0000
> 
> And I have to add -- wow, "quit()" exiting gdb is really nasty
> in that case.  It's even suggested if you try "quit" without
> parens:
> 
>  >>> quit
>  Use quit() or Ctrl-D (i.e. EOF) to exit
> 
> Clearly the embedded use case wasn't considered here.  I think
> this should be reported to Python upstream.

How does one do that?

And btw, while I have your attention: an Emacs user reported a problem
whereby he couldn't find a way of exiting the "pi" invoked from the
GDB session started by "M-x gdb" (which uses GDB/MI) in Emacs.  See
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39140.  I proposed a
solution to that in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39140#8,
which seems to work for me, but that user said it didn't help on his
system.  Does that patch work for others here, or is it the GNU/Linux
system I used to test (fencepost.gnu.org, btw) which is the odd one
out?

P.S. As you might guess, that bug report was the trigger for my
question here.

Thanks.