In article <146f6796-37b5-4220-bdb1-5119cb3ac...@z6g2000pre.googlegroups.com>, Graham Dumpleton <graham.dumple...@gmail.com> wrote:
> On Jan 30, 9:53 am, Ron Garret <rnospa...@flownet.com> wrote: > > In article <498171a5$0$3681$426a7...@news.free.fr>, > > Bruno Desthuilliers <bruno.42.desthuilli...@websiteburo.invalid> > > > > wrote: > > > Ron Garret a écrit : > > > > In article <mailman.8228.1233179089.3487.python-l...@python.org>, > > > > Aleksandar Radulovic <a...@a13x.net> wrote: > > > (snip) > > > >> Secondly, why are you restarting apache after code changes? In normal > > > >> circumstances, you shouldn't have to do that. > > > > > > I thought (and experiment confirms) that only the main WSGI app file > > > > gets reloaded automatically when it changes, not the libraries. > > > > > Depends on how you configure mod_wsgi. Read the part about "Process > > > Reloading Mechanism" here: > > >http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode > > > > I'm running Debian Etch, which means I have an older version of > > mod_wsgi, which means I don't have the process reloading mechanism. > > Back port available at: > > http://packages.debian.org/etch-backports/libapache2-mod-wsgi > > Graham Cool! Thanks! rg
-- http://mail.python.org/mailman/listinfo/python-list