[mod_python] Directory wildcard handling

Graham Dumpleton grahamd at dscpl.com.au
Wed Jul 13 19:13:58 EDT 2005

When suggesting patches, you should also log them in JIRA, first making
sure that it isn't already a known issue. This is better than posting 
only to the mailing list as the mailing list archive is a bit broken and
attachments aren't currently accessible from the web interface to the
archive and therefore patches will most likely be lost.

The JIRA bug tracking system can be found at:


On 14/07/2005, at 8:59 AM, Kevin Quick wrote:

> Attached is a patch that does two things:
> 1) On module import failures, logfile contains additional information 
> showing
>    system paths as well as module name.
> 2) Support of Python*Handler found in a wildcard-based directory.  For 
> example,
> <IfModule mod_python.c>
>     <Directory /home/*/public_html/python>
>         AddHandler mod_python .py
>         PythonHandler helloworld
>         PythonDebug on
>     </Directory>
> </IfModule>
> which mirrors a corresponding perl setting and would allow the user to
> place a mod_python handler in their $HOME/public_html/python directory.
> In the current code, the wildcard is not translated, the sys.path 
> update
> will be invalid, and the user's module will not be accessible.  The 
> attached
> patch provides a fix for this.
> N.B. There are obvious security issues in using this type of 
> configuration,
> but this is very useful for dev environments, and security would 
> implemented
> via explicit alternatives anyhow.
> -- 
> -KQ
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/
> <kwq_path_cvsdiff.diff>_______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://mailman.modpython.org/mailman/listinfo/mod_python

More information about the Mod_python mailing list