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 sbt
Recipients giampaolo.rodola, gvanrossum, jcea, neologix, pitrou, sbt, trent
Date 2013-01-22.15:00:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358866856.49.0.992194620767.issue16507@psf.upfronthosting.co.za>
In-reply-to
Content
According to Alan Cox

    It's a design decision and a huge performance win. It's one of the areas
    where POSIX read in its strictest form cripples your performance.

See https://lkml.org/lkml/2011/6/18/103

> (For write ready, you can obviously have "spurious" notifications if
> you try to write more than what is available in the output socket
> buffer).

Wouldn't you just get a partial write (assuming an AF_INET, SOCK_STREAM socket)?
History
Date User Action Args
2013-01-22 15:00:56sbtsetrecipients: + sbt, gvanrossum, jcea, pitrou, giampaolo.rodola, trent, neologix
2013-01-22 15:00:56sbtsetmessageid: <1358866856.49.0.992194620767.issue16507@psf.upfronthosting.co.za>
2013-01-22 15:00:56sbtlinkissue16507 messages
2013-01-22 15:00:56sbtcreate