|
1 | | -<!-- $Header: /cvsroot/pgsql/doc/src/sgml/plpython.sgml,v 1.17 2003/06/30 18:31:41 tgl Exp $ --> |
| 1 | +<!-- $Header: /cvsroot/pgsql/doc/src/sgml/plpython.sgml,v 1.18 2003/07/01 13:52:29 tgl Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="plpython"> |
4 | 4 | <title>PL/Python - Python Procedural Language</title> |
@@ -90,18 +90,13 @@ def __plpython_procedure_myfunc_23456(): |
90 | 90 | available to all Python functions within a session. Use with care. |
91 | 91 | </para> |
92 | 92 |
|
93 | | -<!-- NOT CORRECT ANYMORE, IS IT? |
94 | | - |
95 | 93 | <para> |
96 | | - Each function gets its ownrestrictedexecutionobject in the |
| 94 | + Each function gets its own executionenvironment in the |
97 | 95 | Python interpreter, so that global data and function arguments from |
98 | 96 | <function>myfunc</function> are not available to |
99 | 97 | <function>myfunc2</function>. The exception is the data in the |
100 | 98 | <varname>GD</varname> dictionary, as mentioned above. |
101 | 99 | </para> |
102 | | - |
103 | | ---> |
104 | | - |
105 | 100 | </sect1> |
106 | 101 |
|
107 | 102 | <sect1 id="plpython-trigger"> |
|