From dc8dec6a70158758b3deeb0da193277ac3699385 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Tue, 1 Jul 2003 13:52:29 +0000
Subject: [PATCH] Fix documentation comment about restricted environments, per
 Kevin Jacobs.

---
 doc/src/sgml/plpython.sgml | 9 ++-------
 1 file changed, 2 insertions(+), 7 deletions(-)

diff --git a/doc/src/sgml/plpython.sgml b/doc/src/sgml/plpython.sgml
index 2de2e746b5f..0a101384ee7 100644
--- a/doc/src/sgml/plpython.sgml
+++ b/doc/src/sgml/plpython.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/plpython.sgml,v 1.17 2003/06/30 18:31:41 tgl Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/plpython.sgml,v 1.18 2003/07/01 13:52:29 tgl Exp $ -->
 
 <chapter id="plpython">
  <title>PL/Python - Python Procedural Language</title>
@@ -90,18 +90,13 @@ def __plpython_procedure_myfunc_23456():
    available to all Python functions within a session.  Use with care.
   </para>
 
-<!-- NOT CORRECT ANYMORE, IS IT?
-
   <para>
-   Each function gets its own restricted execution object in the
+   Each function gets its own execution environment in the
    Python interpreter, so that global data and function arguments from
    <function>myfunc</function> are not available to
    <function>myfunc2</function>.  The exception is the data in the
    <varname>GD</varname> dictionary, as mentioned above.
   </para>
-
--->
-
  </sect1>
 
  <sect1 id="plpython-trigger">
-- 
2.39.5