PythonImport that works for any interpreter.

[Graham Dumpleton <gr...@dscpl.com.au>]

In:

  http://issues.apache.org/jira/browse/MODPYTHON-117

I describe the idea of having a means of using PythonImport to define a
module to be imported into any interpreter that may be created. For some
cases where there are a lot of virtual hosts, this may be simpler than
having to list a directive for every virtual host explicitly.

Is there any interest in such a feature?

If of interest, for a simple implementation, the only issue is one of
ordering when for an interpreter there are both imports for all
interpreters and an interpreter specific imports. Does one import the
module specified to be imported in all interpreters first before the
interpreter specific ones or vice versa.

My feeling has been that the modules to be imported in all intrepreters
should be done first.

Feedback?

Am I wasting my time implementing this one?

Graham

Re: PythonImport that works for any interpreter.

[Jim Gallacher <jp...@jgassociates.ca>]

Graham Dumpleton wrote:
> In:
> 
>   http://issues.apache.org/jira/browse/MODPYTHON-117
> 
> I describe the idea of having a means of using PythonImport to define a
> module to be imported into any interpreter that may be created. For some
> cases where there are a lot of virtual hosts, this may be simpler than
> having to list a directive for every virtual host explicitly.
> 
> Is there any interest in such a feature?
> 
> If of interest, for a simple implementation, the only issue is one of
> ordering when for an interpreter there are both imports for all
> interpreters and an interpreter specific imports. Does one import the
> module specified to be imported in all interpreters first before the
> interpreter specific ones or vice versa.
> 
> My feeling has been that the modules to be imported in all intrepreters
> should be done first.
> 
> Feedback?
> 
> Am I wasting my time implementing this one?

That's entirely up to you. It's not a feature that I need, so don't do 
it on my account. ;)

Jim