On Jun 26, 11:28 am, "Marty Alchin" <[EMAIL PROTECTED]> wrote: > The biggest hurdle to dbsettings at this point is that it caches > settings in a standard Python module, which only exists within a > single process. This was all well and good while developing it, but > people are now starting to try it under mod_python, which (depending > on the Apache MPM) creates multiple processes, each with their own > dbsettings cache. This is fine except when editing settings, since it > can only update the cache in the current process.
Stop me if you've heard this: This is not a bug, it's a feature. Really, though, that's what it is. mod_python is chosen for deployment environments where a person does _NOT_ want a check to occur for updates because it impacts performance, instead choosing to push updates to the server explicitly. An easy way to do this for developers is a command like this: apache[2]ctl graceful|restart Do NOT do your development under mod_python! That is _NOT_ what it's intended for. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
