Terry J. Reedy added the comment:

Makes sense now. Large file relative to machine speed + quick close click = 
close (at least to point of destruction of self.text) before initialization is 
complete.  Hence continued initialization fails. Yes, when closing crashed in 
Multicall, would not see initialization after close error.

Switch to .update_idletasks ignores close event, hence initialization gets to 
complete without error.  Do we want to do that?  I think not.  If one tries to 
edit gigabyte file, idle/tk will probably hang and one very well might want 
close event handled.  We could instead wrap test.tag_config with try: except 
AttributeError.  Original authors assumed this would never happen, but its 
occurrence seems like a rare but legitimate possibility that should be allowed 
for.

After sleeping, I will try to reproduce on my fast machine using Windows copy 
command.  3k EditorWindow.py is colorized too fast.

----------
versions: +Python 3.5

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue22614>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to