[TurboGears] Re: Kid templates not recompiled on change
2006/2/7, Elvelind Grandin [EMAIL PROTECTED]: It does look like some bug. there is no call to cherrypy.server.restart() anywhere except from in a couple of tests. Seems that there is something wrong with Kid :( The log messages are: 2006-02-07 13:08:10,937 turbokid.kidsupport DEBUG Applying template myproject.templates.index 07/Feb/2006:13:08:10 HTTP INFO SystemExit raised: shutting down autoreloader After that Cherrypy gets restarted. It happens on every request. -- Ksenia
[TurboGears] Re: Kid templates not recompiled on change
2006/2/7, Ksenia Marasanova [EMAIL PROTECTED]: Seems that there is something wrong with Kid :( ... and / or autoreload. Setting autoreload.on = False fixes the problem. -- Ksenia
[TurboGears] Re: Kid templates not recompiled on change
Make sure you've got the latest Kid and TurboKid installed... Kevin On 2/7/06, Ksenia Marasanova [EMAIL PROTECTED] wrote: 2006/2/7, Ksenia Marasanova [EMAIL PROTECTED]: Seems that there is something wrong with Kid :( ... and / or autoreload. Setting autoreload.on = False fixes the problem. -- Ksenia -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
[TurboGears] Re: Kid templates not recompiled on change
On 2/5/06, Elvelind Grandin [EMAIL PROTECTED] wrote: for me it takes 0.2 sec to restart cherrypy, even if it takes much longer to start it. The only problem is, as Kevin said, if you have multiple requests at once, especially if you have a lot of images and ajax requests going on at the same time, a majority of those will fail if CP is restarted on every request. If you ask me that's just asking for trouble. :) Lee
[TurboGears] Re: Kid templates not recompiled on change
Max Ischenko [EMAIL PROTECTED] writes: I'm not sure whose fault this is and thus decided to bring this issue to the mailing list. IMO, this is TurboKid that knows whether templates should be reloaded on change and then check this particular template needs refreshing and then signaling Kid to reload it (e.g. delete module from the sys.modules global). On the other hand, when I modify my templates here and just press reload on the browser then I get the new version... Are you modifying things on production or development mode? -- Jorge Godoy [EMAIL PROTECTED]
[TurboGears] Re: Kid templates not recompiled on change
On the other hand, when I modify my templates here and just press reload on the browser then I get the new version... Which version of Kid you're using? I've installed Kid from thirdparty, that's Kid 0.9a. Are you modifying things on production or development mode? development.
[TurboGears] Re: Kid templates not recompiled on change
Max Ischenko [EMAIL PROTECTED] writes: On the other hand, when I modify my templates here and just press reload on the browser then I get the new version... Which version of Kid you're using? Everything from TG trunk. So it is whatever Kevin has flagged to be used with the trunk. I've installed Kid from thirdparty, that's Kid 0.9a. That's what I use. [EMAIL PROTECTED] ~/desenvolvimento/python/TurboGears/trunk/thirdparty/kid % LANG= svn info Path: . URL: svn://lesscode.org/kid/trunk Repository UUID: 2e2b2306-ebee-0310-be8d-abc9dabbc1eb Revision: 265 Node Kind: directory Schedule: normal Last Changed Author: cito Last Changed Rev: 265 Last Changed Date: 2006-01-30 11:17:20 -0200 (Mon, 30 Jan 2006) Properties Last Updated: 2006-01-10 19:39:30 -0200 (Tue, 10 Jan 2006) [EMAIL PROTECTED] ~/desenvolvimento/python/TurboGears/trunk/thirdparty/kid % Are you modifying things on production or development mode? development. Same as here with me. And I have the feeling that templates on development mode are recompiled everytime. -- Jorge Godoy [EMAIL PROTECTED]
[TurboGears] Re: Kid templates not recompiled on change
This should work find for the top level templates. Base templates are a little harder. I had a fix in at one time that made it work, but unfortunately an least 25% of the people who tried it had other issues. Since I could never reproduce on my system I could not debug it. I had to roll out the change since those that did have the problem could not debug it. Try adding kid.reloadbases = True to your config file and see it that helps. Random idea and I am not sure why I didn't think of this sooner...maybe restart cherry after each request in development mode. Why wait to detect that something has changed?-- Davidhttp://www.traceback.org
[TurboGears] Re: Kid templates not recompiled on change
This will work for sure, but on my system CherryPy takes 2 sec. to restart so I will find it quite annoying and not *turbo* if it restarts on every request. ;-) Ciao Michele David Stanek wrote: This should work find for the top level templates. Base templates are a little harder. I had a fix in at one time that made it work, but unfortunately an least 25% of the people who tried it had other issues. Since I could never reproduce on my system I could not debug it. I had to roll out the change since those that did have the problem could not debug it. Try adding kid.reloadbases = True to your config file and see it that helps. Random idea and I am not sure why I didn't think of this sooner...maybe restart cherry after each request in development mode. Why wait to detect that something has changed? -- David http://www.traceback.org
[TurboGears] Re: Kid templates not recompiled on change
On 2/5/06, David Stanek [EMAIL PROTECTED] wrote: Random idea and I am not sure why I didn't think of this sooner...maybe restart cherry after each request in development mode. Why wait to detect that something has changed? As Michele said, it could take some time to restart... *and* a single page view may require multiple hits to CherryPy, which could get ugly. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com
[TurboGears] Re: Kid templates not recompiled on change
for me it takes 0.2 sec to restart cherrypy, even if it takes much longer to start it. On 2/5/06, Kevin Dangoor [EMAIL PROTECTED] wrote: On 2/5/06, David Stanek [EMAIL PROTECTED] wrote: Random idea and I am not sure why I didn't think of this sooner...maybe restart cherry after each request in development mode. Why wait to detect that something has changed? As Michele said, it could take some time to restart... *and* a single page view may require multiple hits to CherryPy, which could get ugly. Kevin -- Kevin Dangoor Author of the Zesty News RSS newsreader email: [EMAIL PROTECTED] company: http://www.BlazingThings.com blog: http://www.BlueSkyOnMars.com -- cheers elvelind grandin
