Jorey Bump writes:
Graham Dumpleton wrote:
The whole point of the changes which were made was to draw a well
defined line between the code modules used in the web application and
which reside in the document tree, or other specially specified areas
by way of mod_python module importer
In mod_python 3.2.x, if I set a directory to use mod_python with a
.htaccess file, I will find that directory in sys.path. That is, if:
/var/www/somedir/.htaccess
contains:
SetHandler python-program
then sys.path will have /var/www/somedir as element zero.
With 3.3.x this does not
In mod_python 3.2.x, if I set a directory to use mod_python with a
.htaccess file, I will find that directory in sys.path. That is, if:
/var/www/somedir/.htaccess
contains:
SetHandler python-program
then sys.path will have /var/www/somedir as element zero.
With 3.3.x this does not
Graham Dumpleton writes:
Read:
http://www.modpython.org/live/current/doc-html/pyapi-apmeth.html
Especially the area which starts just before:
PythonOption mod_python.importer.path ['~']
Your particular issue is mentioned just after this example.
Doesn't work, either in .htaccess
On 18/05/07, Daniel J. Popowich [EMAIL PROTECTED] wrote:
Graham Dumpleton writes:
Read:
http://www.modpython.org/live/current/doc-html/pyapi-apmeth.html
Especially the area which starts just before:
PythonOption mod_python.importer.path ['~']
Your particular issue is mentioned just
I worked it out. As my change didn't disable the mpservlets caching
system, it was never triggering the module importer again to perform
its own checks. Thus, if I add:
klass, cached_mtime, servlets = self.class_cache.get(fname,
