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 CurtHagenlocher
Recipients CurtHagenlocher, akuchling, draghuram, pitrou, schmir
Date 2008-04-15.20:45:14
SpamBayes Score 0.0973155
Marked as misclassified No
Message-id <1208292316.49.0.00492747511517.issue2632@psf.upfronthosting.co.za>
In-reply-to
Content
At least in 2.5.2, there appear to be only two places in the standard 
library where an arbitrary and unchecked size is passed directly to 
_socketobject.recv.  _fileobject.read is one such place and the other 
is in logging/config.py.  In both cases, the pattern is something like

while len(data) < size:
    data = data + sock.recv(size - len(data))

Of course, the same pattern may exist in any number of instances of 
user code that performs a socket.recv, and all of these would be 
subject to the same memory thrashing problem that originally beset 
imaplib.

As such, I now agree with Ralf that the fix ultimately belongs in 
_socketobject.  However, deploying a fix for 2.5.2 is probably easier 
if it's in socket.py than if it requires a recompile.
History
Date User Action Args
2008-04-15 20:45:17CurtHagenlochersetspambayes_score: 0.0973155 -> 0.0973155
recipients: + CurtHagenlocher, akuchling, pitrou, draghuram, schmir
2008-04-15 20:45:16CurtHagenlochersetspambayes_score: 0.0973155 -> 0.0973155
messageid: <1208292316.49.0.00492747511517.issue2632@psf.upfronthosting.co.za>
2008-04-15 20:45:15CurtHagenlocherlinkissue2632 messages
2008-04-15 20:45:14CurtHagenlochercreate