On Wed, Jun 27, 2007 at 02:41:15PM -0000, Donny wrote: > > 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.
I think you've misunderstood Marty. He is not talking about modifying settings.py, he is talking about his dbsettings django app, which stores some parameters in the database. These parameters are intended to be changed by non-developers, and shouldn't require an apache restart to take effect. -Forest
signature.asc
Description: Digital signature
