quetz-mod_python-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Graham Dumpleton <grah...@dscpl.com.au>
Subject Re: [jira] Resolved: (MODPYTHON-118) Allow PythonImport to optionally call function in module.
Date Fri, 17 Mar 2006 04:22:36 GMT
Note that the changes committed for this created a new file:

   test/htdocs/dummymodule.py

Previously, this was created on demand by test/test.py.

Because the "clean" target doesn't remove this old version
created by test/test.py, when you do a "svn update" it will
complain the file already exists as a non versioned file.

You will need to remove the file before doing "svn update".

Graham

On 17/03/2006, at 3:17 PM, Graham Dumpleton (JIRA) wrote:

>      [ http://issues.apache.org/jira/browse/MODPYTHON-118?page=all ]
>
> Graham Dumpleton resolved MODPYTHON-118:
> ----------------------------------------
>
>     Fix Version: 3.3
>      Resolution: Fixed
>
>> Allow PythonImport to optionally call function in module.
>> ---------------------------------------------------------
>>
>>          Key: MODPYTHON-118
>>          URL: http://issues.apache.org/jira/browse/MODPYTHON-118
>>      Project: mod_python
>>         Type: Wish
>>   Components: core
>>     Versions: 3.3
>>     Reporter: Graham Dumpleton
>>     Assignee: Graham Dumpleton
>>      Fix For: 3.3
>
>>
>> PythonImport can currently be used to specify that a module be  
>> imported into a named interpreter at the time that an Apache child  
>> process is initiated. Because all it does is import the module, if  
>> any specific action needs to be triggered, it has to be done as a  
>> side effect of the module import.
>> Triggering  actions as a side effect of a module import is  
>> generally not a good idea as failure of the side effect action  
>> will cause the import of the module itself to fail if the code  
>> doesn't properly handle this situation. It is generally preferable  
>> to import the module and when that has suceeded only then call a  
>> specific function contained in the module to initiate the action.
>> Thus proposed that PythonImport be able to take an optional  
>> function to be called upon successful import of the name module.  
>> The syntax would be like that for Python*Handler directives.
>>   PythonImport mymodule::myfunc myinterpreter
>> This would have the effect of loading module "mymodule" in the  
>> interpreter called "myinterpreter" and then calling  
>> "mymodule.myfunc()". No arguments would be supplied to the  
>> function when called.
>> Another benefit of this feature would be that it would allow a  
>> single module to be able to contain a number of special  
>> initialisation functions that might be triggerable. The user could  
>> selectively call those that might be required.
>>   PythonImport mymodule::enable_caching myinterpreter
>>   PythonImport mymodule::disable_logging myinterpreter
>> At the moment to do that, a distinct module would need to be  
>> created for each where the only thing in the module is the call of  
>> the function.
>> Note that in using something similar to mod_python option/config  
>> values, am talking here about options that must be able to only be  
>> enabled/disable in one spot. The problem with mod_python option/ 
>> config values in Apache is that different parts of the document  
>> tree can set them to different values, which for some things is  
>> actually a problem, such as the case with PythonAutoReload.
>
> -- 
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the  
> administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
>    http://www.atlassian.com/software/jira


Mime
View raw message