Graham Dumpleton wrote:
On 10/06/2005, at 2:53 AM, dharana wrote:
As for vampire - why would I want vampire? mod_python is great
except this. I personally have no interest in adding yet more
software to my system just to solve the mod_python import issue -
Id rather it was fixed in the
On 09/06/2005, at 4:38 PM, Nicolas Lehuen wrote:
Erm, so, no, handlers could also be imported from the document tree.
No problem, we can do that, but the security issues pop up once again.
We can't protect against everything though. ;-)
I've understood you point, but there is a difficulty
I find that I'm unable to follow the import discussion in an e-mail
exchange format. This is a complex issue that requires a lot of things to
be considered, researched, tested, etc. I find that as I read these
e-mails I find points that are potentially contestable, but to
meaningfully
2005/6/8, Graham Dumpleton [EMAIL PROTECTED]:
c) the apache.import_module() function, which is frankly a strange
beast. It knows how to approximately reload some modules, but has many
tricks that makes it frankly dangerous, namely the one that causes
modules with the same name but residing
Barry Pearce wrote:
As for user imports in general, I would prefer that everything work in
a standard Python way out of the box. mod_python should be what it is
-- an interface to apache. That's most useful for application and
framework developers I think. Otherwise you could end up
On 09/06/2005, at 12:29 AM, Nick wrote:
but I just want to be clear that I don't think mod_python should
install any import hooks. That would probably be annoying to seasoned
Python programmers, and really a pain in the butt for me specifically.
Curious to know why you think this would be
Graham Dumpleton wrote:
On 09/06/2005, at 12:29 AM, Nick wrote:
but I just want to be clear that I don't think mod_python should
install any import hooks. That would probably be annoying to seasoned
Python programmers, and really a pain in the butt for me specifically.
Curious to know why
Nick, what do you think about apache.import_module, as it is now
and/or as I've described before ?
Let's forget about the import hook, let's say import is for standard
modules only. What do you think about providing our users a way to
dynamically import some modules without polluting sys.modules
Yeah I totally agree that something needs to be done there. It's a good
utility to have in the mod_python toolbox, and there is a definite need.
I've looked at Graham's code for caching modules, and it does a good job.
If something like that could be included in mod_python, probably in
On 09/06/2005, at 8:04 AM, Nick wrote:
Graham Dumpleton wrote:
On 09/06/2005, at 12:29 AM, Nick wrote:
but I just want to be clear that I don't think mod_python should
install any import hooks. That would probably be annoying to
seasoned Python programmers, and really a pain in the butt
Graham Dumpleton wrote:
The apache.import_module() method is already currently used to perform the
top level import of a handler module and already behaves differently to a
standard import, so even without an import hook you already have a
problem.
You're right; when I hit apache with ab, I
On 08/06/2005, at 8:33 AM, Barry Pearce wrote:
Indeed Im for fixing it...its on my list of things to do...right after
'do everything the company want RSN'
I do believe it should be mod_python that is fixed. I have a VERY big
need for reload of modules *without* taking down my server -
12 matches
Mail list logo
