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 neologix
Recipients Alexey.Agapitov, Benjamin.Ash, giampaolo.rodola, neologix, python-dev, rosslagerwall, vstinner
Date 2013-02-04.18:28:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0=hqA_7jk_BYz4hNRMQWmK+S=vw4ZRu5tBGFB5AgkFug@mail.gmail.com>
In-reply-to <1359995486.55.0.675667544046.issue12502@psf.upfronthosting.co.za>
Content
> Using handle_accept() in my code and remembering to call listen() in my
> asyncore.dispatcher server's constructor did the trick.
>
> I am not sure if we still have a bug here though, since if the subclass
> doesn't define  a proper handle_accept() we get into the select() loop and
> 100% CPU utilization after the initial client connection.

No, it's not a bug.
The attached test case was for Python 3: Python 2 doesn't have
handle_accepted(), and since the default implementation of
handle_accept() doesn't nothing, the handler is called in a loop,
because the socket is effectively always ready for accept.
History
Date User Action Args
2013-02-04 18:28:33neologixsetrecipients: + neologix, vstinner, giampaolo.rodola, rosslagerwall, python-dev, Alexey.Agapitov, Benjamin.Ash
2013-02-04 18:28:33neologixlinkissue12502 messages
2013-02-04 18:28:33neologixcreate