New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
asyncore loop lacks timers and work tasks #46290
Comments
I've been reading asyncore lately, and feel that it's showing its age. |
Looks like Giampaolo has already submitted a patch for part of this, in |
If you are going to spend some time with async event io you may be |
I'm not sure to understand what do you mean by "work tasks".
Absolutely. I'd have some ideas about some asyncore/chat enhancements, |
*I'm not sure to understand what do you mean by "work tasks".* They're low-priority tasks that need to get run sometime, but aren't *writing a poller suitable with epoll and kqueue* Christian's patch looks interesting, in that respect. I haven't applied it Bill On Feb 4, 2008 2:00 PM, Giampaolo Rodola' <report@bugs.python.org> wrote:
|
I still don't get it. Maybe you're talking about something like "call a
function at the next select() loop" which in Twisted is equal to:
>>> reactor.callLater(0, something)
By using my patched asyncore you can do the same with:
>>> self.call_later(0, something) |
Yes, that's it exactly. So things without work tasks can still get done. But timers are the important thing. With timers you can always implement On Feb 6, 2008 12:49 PM, Giampaolo Rodola' <report@bugs.python.org> wrote:
|
Sorry, I meant to say, "so things without input FDs can make progress". On Feb 6, 2008 8:08 PM, Bill Janssen <bill.janssen@gmail.com> wrote:
|
I have the feeling that you're talking about the same thing.
Note that "something" is any callable object ('e.g. lambda: print |
Yes, I think we're talking about the same thing, too. |
Since this seems to be a duplicate of bpo-1641 I propose to close this issue. |
Because of Giampaolo suggestion, that is reviewing all these |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: