Re: Sloooooowwwww WSGI restart

2009-01-30 Thread Ron Garret
In article <146f6796-37b5-4220-bdb1-5119cb3ac...@z6g2000pre.googlegroups.com>, Graham Dumpleton wrote: > On Jan 30, 9:53 am, Ron Garret wrote: > > In article <498171a5$0$3681$426a7...@news.free.fr>, > >  Bruno Desthuilliers > > > >  wrote: > > > Ron Garret a écrit : > > > > In article , > > >

Re: Sloooooowwwww WSGI restart

2009-01-29 Thread Graham Dumpleton
On Jan 30, 9:53 am, Ron Garret wrote: > In article <498171a5$0$3681$426a7...@news.free.fr>, >  Bruno Desthuilliers > >  wrote: > > Ron Garret a écrit : > > > In article , > > >  Aleksandar Radulovic wrote: > > (snip) > > >> Secondly, why are you restarting apache after code changes? In normal >

Re: Sloooooowwwww WSGI restart

2009-01-29 Thread Ron Garret
In article <498170d4$0$23718$426a7...@news.free.fr>, Bruno Desthuilliers wrote: > Ron Garret a écrit : > > I'm running a WSGI app under apache/mod_wsgi and I've noticed that > > whenever I restart the server after making a code change it takes a very > > long time (like a minute) before the

Re: Sloooooowwwww WSGI restart

2009-01-29 Thread Ron Garret
In article <498171a5$0$3681$426a7...@news.free.fr>, Bruno Desthuilliers wrote: > Ron Garret a écrit : > > In article , > > Aleksandar Radulovic wrote: > (snip) > >> Secondly, why are you restarting apache after code changes? In normal > >> circumstances, you shouldn't have to do that. > > >

Re: Sloooooowwwww WSGI restart

2009-01-29 Thread Aleksandar Radulovic
Graham, On Thu, Jan 29, 2009 at 1:00 PM, Graham Dumpleton wrote: > In other words, it is not universal that any code change will be > automatically detected and a reload occur. There are also various > caveats on what mod_python module importer does, as it is reloading > modules into an existing

Re: Sloooooowwwww WSGI restart

2009-01-29 Thread Graham Dumpleton
On Jan 29, 8:15 pm, Aleksandar Radulovic wrote: > Graham, > > On Thu, Jan 29, 2009 at 1:16 AM, Graham Dumpleton > > wrote: > > Sorry, you are wrong to assume that an Apache restart is not be > > required. > > If you are usingmod_wsgiembedded mode, or mod_python, then a code > > change will always

Re: Sloooooowwwww WSGI restart

2009-01-29 Thread Aleksandar Radulovic
Graham, On Thu, Jan 29, 2009 at 1:16 AM, Graham Dumpleton wrote: > Sorry, you are wrong to assume that an Apache restart is not be > required. > If you are using mod_wsgi embedded mode, or mod_python, then a code > change will always require a full restart of Apache. I am running several middlew

Re: Sloooooowwwww WSGI restart

2009-01-29 Thread Bruno Desthuilliers
Ron Garret a écrit : In article , Aleksandar Radulovic 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

Re: Sloooooowwwww WSGI restart

2009-01-29 Thread Bruno Desthuilliers
Ron Garret a écrit : I'm running a WSGI app under apache/mod_wsgi and I've noticed that whenever I restart the server after making a code change it takes a very long time (like a minute) before the script is active again. In other words, I do an apachectl restart, reload the page in my browser

Re: Sloooooowwwww WSGI restart

2009-01-28 Thread Ron Garret
In article <4cd232ff-ba8b-47aa-8ee6-d8d9712db...@s1g2000prg.googlegroups.com>, Graham Dumpleton wrote: > On Jan 29, 8:35 am, Ron Garret wrote: > > I'm running a WSGI app under apache/mod_wsgiand I've noticed that > > whenever I restart the server after making a code change it takes a very > >

Re: Sloooooowwwww WSGI restart

2009-01-28 Thread Graham Dumpleton
On Jan 29, 8:44 am, Aleksandar Radulovic wrote: > Hi there, > > On Wed, Jan 28, 2009 at 9:35 PM, Ron Garret wrote: > > I'm running a WSGI app under apache/mod_wsgiand I've noticed that > > Off the bat, there's no reason to run an app under apache/mod_wsgi > while developing it, > ie. if u use Pyl

Re: Sloooooowwwww WSGI restart

2009-01-28 Thread Ron Garret
In article , Jean-Paul Calderone wrote: > On Wed, 28 Jan 2009 13:35:56 -0800, Ron Garret wrote: > >I'm running a WSGI app under apache/mod_wsgi and I've noticed that > >whenever I restart the server after making a code change it takes a very > >long time (like a minute) before the script is act

Re: Sloooooowwwww WSGI restart

2009-01-28 Thread Ron Garret
In article , Aleksandar Radulovic wrote: > Hi there, > > On Wed, Jan 28, 2009 at 9:35 PM, Ron Garret wrote: > > I'm running a WSGI app under apache/mod_wsgi and I've noticed that > > Off the bat, there's no reason to run an app under apache/mod_wsgi > while developing it, > ie. if u use Pylon

Re: Sloooooowwwww WSGI restart

2009-01-28 Thread Graham Dumpleton
On Jan 29, 8:35 am, Ron Garret wrote: > I'm running a WSGI app under apache/mod_wsgiand I've noticed that > whenever I restart the server after making a code change it takes a very > long time (like a minute) before the script is active again.  In other > words, I do an apachectl restart, reload t

Re: Sloooooowwwww WSGI restart

2009-01-28 Thread Aleksandar Radulovic
Hi there, On Wed, Jan 28, 2009 at 9:35 PM, Ron Garret wrote: > I'm running a WSGI app under apache/mod_wsgi and I've noticed that Off the bat, there's no reason to run an app under apache/mod_wsgi while developing it, ie. if u use Pylons or TurboGears, there's an easier way to serve the app (usi

Re: Sloooooowwwww WSGI restart

2009-01-28 Thread Jean-Paul Calderone
On Wed, 28 Jan 2009 13:35:56 -0800, Ron Garret wrote: I'm running a WSGI app under apache/mod_wsgi and I've noticed that whenever I restart the server after making a code change it takes a very long time (like a minute) before the script is active again. In other words, I do an apachectl restar

Sloooooowwwww WSGI restart

2009-01-28 Thread Ron Garret
I'm running a WSGI app under apache/mod_wsgi and I've noticed that whenever I restart the server after making a code change it takes a very long time (like a minute) before the script is active again. In other words, I do an apachectl restart, reload the page in my browser, and one minute late