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 diekmann
Recipients diekmann, pitrou
Date 2010-12-08.10:17:06
SpamBayes Score 3.3238817e-07
Marked as misclassified No
Message-id <1291803430.7.0.25296396852.issue10644@psf.upfronthosting.co.za>
In-reply-to
Content
The Documentation states:

socket.sendall(bytes[, flags])¶
    Send data to the socket. The socket must be connected to a remote socket. The optional flags argument has the same meaning as for recv() above. Unlike send(), this method continues to send data from bytes until either all data has been sent or an error occurs. None is returned on success. On error, an exception is raised, and there is no way to determine how much data, if any, was successfully sent.

This is not consistent with the results reproduced above, however, the results from above are exactly what should happen. Maybe there should be a remark, that the return value of sendall (and send) may be system dependent. Or a patch which enforces the documented behviour of sendall, regardless of the operating system would be a nice future feature?
History
Date User Action Args
2010-12-08 10:17:10diekmannsetrecipients: + diekmann, pitrou
2010-12-08 10:17:10diekmannsetmessageid: <1291803430.7.0.25296396852.issue10644@psf.upfronthosting.co.za>
2010-12-08 10:17:06diekmannlinkissue10644 messages
2010-12-08 10:17:06diekmanncreate