[Webware-devel] Re: [Cheetahtemplate-discuss] 2.0 bugs or warts?

2006-01-25 Thread Ian Bicking
Tavis Rudd wrote: Well, last time I checked, Webware didn't work with them. This was either due to sys.path manipulations at startup or because of 'ImportSpy' - something used to support WebKit's autoreload behavior. If it was the former, I suspect you can resolve the issue by install Cheetah

[Webware-devel] Re: [Cheetahtemplate-discuss] 2.0 bugs or warts?

2006-01-25 Thread Tavis Rudd
last time I checked it was still there, but with a comment with your argument for removal. I agree completely. On Wednesday 25 January 2006 2:29 pm, Ian Bicking wrote: > Tavis Rudd wrote: > > Well, last time I checked, Webware didn't work with them. This was > > either due to sys.path manipulat

Re: [Webware-devel] Re: [Cheetahtemplate-discuss] 2.0 bugs or warts?

2006-01-25 Thread Chuck Esterbrook
I'm working strictly off memory here, but I thought the point of the implementation was that it used a special library (when available) that eliminated the need for polling. Instead, the op sys would notify the appserver process when a file changed. Does that sound familiar? Polling has the well

Re: [Webware-devel] Re: [Cheetahtemplate-discuss] 2.0 bugs or warts?

2006-01-25 Thread Ian Bicking
Chuck Esterbrook wrote: I'm working strictly off memory here, but I thought the point of the implementation was that it used a special library (when available) that eliminated the need for polling. Instead, the op sys would notify the appserver process when a file changed. Does that sound famili