This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients serhiy.storchaka, terry.reedy
Date 2014-10-12.09:32:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1413106337.21.0.96005087212.issue22614@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2014-10-12 09:32:17terry.reedysetrecipients: + terry.reedy, serhiy.storchaka
2014-10-12 09:32:17terry.reedysetmessageid: <1413106337.21.0.96005087212.issue22614@psf.upfronthosting.co.za>
2014-10-12 09:32:17terry.reedylinkissue22614 messages
2014-10-12 09:32:16terry.reedycreate