| Graham Dumpleton (JIRA) 2006-02-13, 8:45 pm |
| [ http://issues.apache.org/jira/brows...action_12366270 ]
Graham Dumpleton commented on MODPYTHON-63:
-------------------------------------------
In what will be the grand unified theory for the module importer, there will be no explicit modification of sys.path, so above solution isn't going to work.
The issues of wildcards in paths does need to be looked at and how they do it in mod_perl would be a good guide so still need to keep this issue open.
FWIW though, the above will be able to be done in other ways when MODPYTHON-125 is addressed. One could for example use:
<IfModule mod_python.c>
<Directory /home/*/public_html/python>
PythonFixupHandler mod_userdir_dispatch
PythonDebug on
</Directory>
</IfModule>
# mod_userdir_dispatch.py
from mod_python import apache
def fixuphandler(req):
if os.splitext(req.filename)[1] == ".py":
req.handler = "mod_python"
user = req.notes["mod_userdir_user"]
directory = "/home/%s/public_html/python" % user
req.add_handler("PythonHandler","helloworld",dir)
return apache.OK
In other words, use a fixup handler to enable mod_python for the content handler phase when extension of mapped file is .py, and also specify actual module in users home directory to be called in that situation.
Personally I wouldn't use "helloworld" in the users directory but something like "_dispatch". That way a user could put in that file:
# _dispatch.py
from mod_python.publisher import handler
Thus allowing them to use publisher, but where an access to URL of "_dispatch.py/handler" isn't going to cause a loop as publisher tries to call into it, ie., the underscore protects it from publisher.
At least I think that would work.
> Handle wildcard in Directory to sys.path transfer
> -------------------------------------------------
>
> Key: MODPYTHON-63
> URL: http://issues.apache.org/jira/browse/MODPYTHON-63
> Project: mod_python
> Type: Improvement
> Components: core
> Versions: 3.1.3
> Environment: gentoo Linux 2.4.20-gentoo-r8 apache-2.0.54-r8 mod_python-3.1.3-r1
> Reporter: Kevin Quick
> Priority: Minor
[vbcol=seagreen]
>
> Below 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.
> Index: apache.py
> ========================================
===========================
> RCS file: /home/cvspublic/httpd-python/lib/python/mod_python/apache.py,v
> retrieving revision 1.83
> diff -r1.83 apache.py
> 33a34,40
> 170,171c177
> < if filter.dir and (filter.dir not in sys.path):
> < sys.path[:0] = [filter.dir]
> ---
> 280,282c286
> < dir = hlist.directory
> < if dir and (dir not in sys.path):
> < sys.path[:0] = [dir]
> ---
> 454c458,462
> < f, p, d = imp.find_module(parts[i], path)
> ---
|