Bug in the webmonitor.py example that causes just one iteration and then stops

[lstep]

The webmonitor.py example, when run, connects just once to the remote web 
server, and then do nothing. The problem is that in the example there is no 
reportNoChange() method in the ChangeNotified class. So when the ChangeChecker 
is called and that there is no change on the page (most usual :), it tries to 
call self.notified.reportNoChange() which doesn't exist ! So it "crashes" 
silently, and you think monitor is working... 
To correct this, just add:: 
 
  def reportNoChange(self): 
          pass 
in the ChangeNotified class of the webmonitor.py example file. 
 
To be more clean, I suggest to add a test for the presence of the methods 
reportNoChange() and reportChange() in t.w.monitor module.

[Moshe Zadka]

Checking in twisted/web/monitor.py;
/cvs/Twisted/twisted/web/monitor.py,v  <--  monitor.py
new revision: 1.7; previous revision: 1.6
done
Fixed [By enhancing BaseChange]

[GitHub <noreply@…>]

In 778eda4f:

Merge pull request #308 from twisted/8573-scop-files

Author: scop
Reviewer: rodrigc
Fixes: #8573

More file close related fixes