Removed Python integration support.

1 files changed, 3 insertions, 44 deletions

diff --git a/ledger.texi b/ledger.texi
index b8da037a..f271f5a1 100644
--- a/ledger.texi
+++ b/ledger.texi
@@ -64,7 +64,6 @@ OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 * Running Ledger::              
 * Keeping a ledger::            
 * Using XML::                   
-* Extending with Python::       
 @end menu
 
 @node Introduction, Running Ledger, Top, Top
@@ -2260,14 +2259,6 @@ precedence order of operators.
 @item [DATE]
 Useful specifying a date in plain terms.  For example, you could say
 @samp{[2004/06/01]}.
-
-@item @@STR(ARGS,...)
-If Python support is compiled in, this calls the Python function
-@code{STR}.  It is always be passed at least one argument, of type
-@var{ledger.Details}, representing the known account, entry, and
-transaction details at the time the value expression is computed.
-Other value expression arguments may also be passed by the user, all
-of type @var{Value}.
 @end table
 
 @node Period expressions, File format, Value expressions, Running Ledger
@@ -2431,13 +2422,6 @@ transactions that follow, until @samp{!end} is seen.
 
 @item !end
 Ends an account block.
-
-@item !python
-If Python support is available, all of the lines following
-@samp{!python} will be passed to the Python interpretor.  Any
-functions defined will be available to later Python blocks, and can be
-called from a value expression.  The Python code block must be ended
-with @samp{!end}.
 @end table
 
 @item ;
@@ -3699,8 +3683,8 @@ description is a ledger account name, these in/out pairs may be viewed
 as virtual transactions, adding time commodities (hours) to that
 account.
 
-For example, the command-line version of the timeclock tool (which is
-written in Python) could be used to begin a timelog file like:
+For example, the command-line version of the timeclock tool could be
+used to begin a timelog file like:
 
 @example
 export TIMELOG=$HOME/.timelog
@@ -3778,7 +3762,7 @@ accounting ledger, with the attached prefix @samp{Billable}:
     Receivable:ClientOne
 @end smallexample
 
-@node Using XML, Extending with Python, Keeping a ledger, Top
+@node Using XML,  , Keeping a ledger, Top
 @chapter Using XML
 
 By default, Ledger uses a human-readable data format, and displays its
@@ -3930,29 +3914,4 @@ output such data if the @command{xml} command is used, and can read
 the same data as long as the @file{expat} library was available
 when Ledger was built.
 
-@node Extending with Python,  , Using XML, Top
-@chapter Extending with Python
-
-Ledger fully supports Python as an extension language.  It may be used
-in a few different forms, which fall into three basic categories:
-
-@enumerate
-@item
-Defining Python functions to use in value expressions
-@item
-Using the ledger library as a Python module
-@item
-Setting up custom initialization using Python
-@end enumerate
-
-Note that this feature, while functional, is still under development.
-It will not be documented until it has been fully proven, probably in
-the next version of ledger.  For now, if you wish to make this of this
-functionality and are willing to debug problems that come up, pass the
-option @samp{--enable-python} to configure, and contact the author via
-email.
-
-One example of using Python to create a more complex report is in the
-script file @file{scripts/trend}.
-
 @bye