svn commit: r481752 - /httpd/mod_python/trunk/Doc/modpython4.tex

[gr...@apache.org]

Author: grahamd
Date: Sun Dec  3 02:37:02 2006
New Revision: 481752

URL: http://svn.apache.org/viewvc?view=rev&rev=481752
Log:
More documentation about apache.import_module(), specifically, how to enable
the old importer.


Modified:
    httpd/mod_python/trunk/Doc/modpython4.tex

Modified: httpd/mod_python/trunk/Doc/modpython4.tex
URL: http://svn.apache.org/viewvc/httpd/mod_python/trunk/Doc/modpython4.tex?view=diff&rev=481752&r1=481751&r2=481752
==============================================================================
--- httpd/mod_python/trunk/Doc/modpython4.tex (original)
+++ httpd/mod_python/trunk/Doc/modpython4.tex Sun Dec  3 02:37:02 2006
@@ -355,8 +355,22 @@
   rely on this documentation and instead refer to the documentation for
   the specific version you are using as the new importer does not behave
   exactly the same and has additional features.
+
+  If you are trying to port code from an older version of mod_python to
+  mod_python 3.3 and can't work out why the new importer is not working
+  for you, you can enable the old module importer for specific Python
+  interpreter instances by using:
+
+  \begin{verbatim}
+    PythonOption mod_python.legacy.importer name
+  \end{verbatim}
+
+  where 'name' is the name of the interpreter instance or '*' for it to
+  be applied to all interpreter instances. This option should be placed
+  at global context within the main Apache configuration files.
 \end{notice}
 
+  When using the \code{apache.import_module()} function, the
   \var{module_name} should be a string containing either the module name,
   or a path to the actual code file for the module; where a module is a
   candidate for automatic module reloading, \var{autoreload} indicates