From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: archer ml <archer@sourceware.org>
Subject: [python] Mention Python help command and keyword arguments convention.
Date: Fri, 27 Feb 2009 20:00:00 -0000 [thread overview]
Message-ID: <1235764818.8949.21.camel@localhost.localdomain> (raw)
Hi,
Just pushed this.
gdb/doc/
* gdb.texinfo (Python API): Mention python help command and
convention for accepting keyword arguments.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 67c0ae3..d055353 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -18114,6 +18114,14 @@ auto-loading is disabled.
@cindex python api
@cindex programming in python
+You can get quick online help for @value{GDBN}'s Python API by issuing
+the command @w{@kbd{python help (gdb)}}.
+
+Functions and methods which have two or more optional arguments allow
+them to be specified using keyword syntax. This allows passing some
+optional arguments while skipping others. Example:
+@w{@code{gdb.some_function ('foo', bar = 1, baz = 2)}}.
+
@cindex python stdout
@cindex python pagination
At startup, @value{GDBN} overrides Python's @code{sys.stdout} and
reply other threads:[~2009-02-27 20:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1235764818.8949.21.camel@localhost.localdomain \
--to=bauerman@br.ibm.com \
--cc=archer@sourceware.org \
/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).