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 righ
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 right place...not everyone uses
Gregory (Grisha) Trubetskoy writes:
>
> 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 potenti
Graham Dumpleton wrote:
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*
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
Graham Dumpleton wrote:
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 think you misunderstand why I'm saying, or maybe I misuderstood Nicolas.
By "Handler" modules I mean your modules that implement accesshand
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 o
2005/6/9, Graham Dumpleton <[EMAIL PROTECTED]>:
> I admit I haven't necessarily fully digested some of what has already been
> proposed but, here is my take on the issue put together on main train ride
> this morning to work .
>
> I feel that there are a lot of issues which need to be covered
Nick wrote ..
> I agree; the code there is relatively simple and will probably do the
> job for most people. Keep it simple, and it can serve as an example for
> people who want to do something more sophisticated. Or they can upgrade
> from publisher to vampire; honestly, if you like publisher I
Graham Dumpleton wrote:
Note that the direction I am looking at here is that apache.import_module()
is made to function properly in the contexts it needs to and not perform
double duty in satisfying extra requirements of top level mod_python imports
where it has to import stuff from site-packages
I admit I haven't necessarily fully digested some of what has already been
proposed but, here is my take on the issue put together on main train ride
this morning to work .
I feel that there are a lot of issues which need to be covered to solve the
problems with module loading. The apache.impo
On Thu, 2005-06-09 at 00:50 +0200, Nicolas Lehuen wrote:
> Most of the problems raised when importing handlers (including double
> import of handlers) have been solved in the trunk for a while now, the
> bug fixes are waiting for an official release.
Looks good, seems to work well. However, I nev
2005/6/9, Nick <[EMAIL PROTECTED]>:
> 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
> > pro
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
On Tue, 7 Jun 2005, Barry Pearce wrote:
I'm not opposed to providing some sort of module or function for psp or
publisher or whatever "example" handlers that come with mod_python, just
so long as it's not in the core of mod_python itself. To me this is an
application/framework issue, not a m
An update on a few things that I have managed to get working in
Vampire in respect of some of the issues below, plus a few other
comments.
On 08/06/2005, at 6:33 AM, Nicolas Lehuen wrote:
One last thing that we should prepare is a clear and definite answer
to the zillion users who need to impor
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 - en
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 - end users
are using it and credit card transactions
One last thing that we should prepare is a clear and definite answer
to the zillion users who need to import a custom utility module.
Today, we have 4 ways of importing code :
a) the standard "import" keyword. Today, it works unchanged
(mod_python doesn't install any import hook). The consequence
19 matches
Mail list logo
