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 josiahcarlson
Recipients
Date 2005-12-15.09:38:00
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=341410

If anything should be changed, I would say the docs.  Though
I disagree with the send during a call to push(), for most
users, it makes sense, and convincing the current maintainer
that removing the send on push for the sake of async purity
would be difficulty (practicality beats purity).

I believe that adding a note which reads something like the
following would be sufficient.
"The default push() implementation calls the underlying
socket send() (to increase data throughput in many
situations), and upon error, will call handle_error().  This
may cause unexpected behavior if push() is used within a
subclassed handle_connect()."
History
Date User Action Args
2007-08-23 14:36:28adminlinkissue1370380 messages
2007-08-23 14:36:28admincreate