On 09/06/2005, at 11:15 PM, Nick wrote:
Graham Dumpleton wrote:
module, from the document tree. Maybe the context of the directive
could be used for that ; if the directive is defined at the server or
virtual host level, then it's a top level handler, otherwise if it is
defined in a Location or Directory (or .htaccess file), then it's a
handler that should be loaded from the document tree (with a possible
fallback to sys.path if it is not found ?).
Aside from the potential security issues of storing your handler
modules in the document tree,
Handler modules in your document tree is done all the time, you can't
avoid
it with mod_python.publisher and most other systems.
I just don't it's a good idea to traverse the document tree for a
python module/package. Even in a shared hosting situation, there are
still ways to store your modules outside the accessible document tree.
I can just see so many confused people wondering why module B was
imported instead of module A, which reside in different parts of the
document tree. And module B isn't even a handler, it's a support
module. Ugly. Not to mention name collision problems that are bound
to happen when per directory interpreters aren't being used in that
situation.
Huh?
We aren't talking about any form of arbitrary traversal of the document
tree.
Overall I am not sure where you are going with this ...
Its getting a bit late for me now to really address these issues
properly plus
what else you said in your email, brain is starting to clag up. I will
say though
that I think I have basically got packages to work now despite what I
said. Just
need to finish a couple of things, clean up code and check that certain
other
usage cases still work.
For me at least, if things can be made to work how people generally
expect them
to work and for it to be transparent, that is better than too many
obscure rules.
Good night from me ...
Graham
