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 known disadvantages of (1) the gap between polls
(too big? too small? never just right), (2) wasted effort checking for
something repeatedly and in this case, (3) the increased amount of
time required per poll as your app grows larger and uses more modules.
Although, I don't see why we couldn't have an option to use one
technique vs. another. We could even default it to polling sys.modules
since that seems less likely to disturb other Python packages like
On 1/25/06, Tavis Rudd <tavis@...> wrote:
> last time I checked it was still there, but with a comment with your argu=
> 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 manipulations at startup or because of 'Import=
> > > - something used to support WebKit's autoreload behavior. If it was =
> > > former, I suspect you can resolve the issue by install Cheetah's hook=
> > > after all the sys.path manipulations are finished.
> > ImportSpy should really just be removed -- periodically scanning
> > sys.modules has the same effect, without an import hook.
> > I thought that change actually happened at some point, but I can't
> > remember.
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> Webware-devel mailing list