[mod_python] The new module loader

Dan Eloff dan.eloff at gmail.com
Wed Apr 19 18:06:30 EDT 2006

I went digging through the mod_python files and discovered how the new
publisher loader works (using ModuleCache) and I borrowed the idea to import
modules for my handler.

The purpose of ModuleCache was to avoid sys.modules right?

I'm having some trouble with this, and I eventually tracked it down to
multiple versions of a dependancy module being loaded.

My handler loads one version, with empty module variables, while the actual
modules for the pages load different version(s) and populate them with data.
The changes are never reflected in the version kept by my handler (because
they are not the same)

This all makes sense, and is probably the intended effect, but what do you
do for modules like Session in mod_python, where MemorySession uses a static
class member to store sessions? Wouldn't the page modules each get their own
version and thusly prevent sessions from working?

I need to be able to reload modified modules, but also to make use of shared
modules. These seem to be conflicting needs, however. Does anybody have any
inisght into this situation that they can share?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mm_cfg_has_not_been_edited_to_set_host_domains/pipermail/mod_python/attachments/20060419/f689f234/attachment.html

More information about the Mod_python mailing list