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 gvanrossum
Recipients Ludovic.Gasc, Maxime S, gvanrossum, serhiy.storchaka, terry.reedy, yselivanov
Date 2016-07-26.15:44:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJJ6kuJYye1XtptxndEF13fUn-fiUvhv2HTwJper3B57aQ@mail.gmail.com>
In-reply-to <1469511676.49.0.5271682939.issue27546@psf.upfronthosting.co.za>
Content
Isn't this going to busy-wait, esp. with the loop.call_soon() version?

Even with loop.call_later(0.1, tk_update) you're wasting battery power
even if no network activity and no UI activity is happening. I'm not
eager to document this as the right way to do things, even if it
unblocks some apps in the short term.

A proper solution IMO should somehow merge the selectors so that a
single select() or whatever wakes up when either network I/O happens
or a UI event comes in (which could be something that Tk transparently
handles but it still needs to be given the chance, through
root.update()).
History
Date User Action Args
2016-07-26 15:44:44gvanrossumsetrecipients: + gvanrossum, terry.reedy, Ludovic.Gasc, serhiy.storchaka, yselivanov, Maxime S
2016-07-26 15:44:44gvanrossumlinkissue27546 messages
2016-07-26 15:44:44gvanrossumcreate