From b9965f813478e09b8e368557f33516def44fb3aa Mon Sep 17 00:00:00 2001 From: guido Date: Tue, 13 Feb 2007 13:49:37 +0100 Subject: [PATCH] [svn r38685] Partial rewrite of fijal's pdb/apigen text. --HG-- branch : trunk --- py/doc/future.txt | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/py/doc/future.txt b/py/doc/future.txt index 815067c64..2b134cc39 100644 --- a/py/doc/future.txt +++ b/py/doc/future.txt @@ -39,12 +39,13 @@ by a py.test run. Consider APIGEN and pdb integration =================================== -Apigen is a source of a great information about functions, -methods and objects. Pdb is a nice tool for debugging. -While not get them together? Imagine the world where you can -ask "info function\_name" and you'll get all the information -regarding types coming, types getting out, possible exceptions, -field types and call sites. +The information provided by APIGEN can be used in many +different ways. An example of this could be to write +an extension to pdb which makes it available. +Imagine you could issue a pdb command +"info " and get information +regarding incoming, and outgoing types, possible +exceptions, field types and call sites. Distribute channels/programs across networks ================================================