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 kristjan.jonsson
Recipients amaury.forgeotdarc, benjamin.peterson, kristjan.jonsson, pitrou
Date 2009-02-03.09:08:56
SpamBayes Score 2.0237309e-08
Marked as misclassified No
Message-id <1233652138.22.0.871974716164.issue4879@psf.upfronthosting.co.za>
In-reply-to
Content
The socket.socket.makefile() now returns a quite different kind of 
object, namely a SocketIO thing.  This comes as a result of the IO 
refactoring in 3.0.
The good side to this is that old and naughty apps have been forbidden 
to access the _sock member directly.  This was the reason that we had 
to disable read buffering in 2.x:  Some clients would read directly 
from the socket, even though it was "hidden".

As for the test failure, I admit that I didn't enable the "network" 
resource for the testsuite.  Will fix.

Btw, test_xmlrpc_net.py fails, because time.xmlrpc.com doesn't 
resolve.  Are there any other good and stable rpc servers out there?
History
Date User Action Args
2009-02-03 09:08:58kristjan.jonssonsetrecipients: + kristjan.jonsson, amaury.forgeotdarc, pitrou, benjamin.peterson
2009-02-03 09:08:58kristjan.jonssonsetmessageid: <1233652138.22.0.871974716164.issue4879@psf.upfronthosting.co.za>
2009-02-03 09:08:57kristjan.jonssonlinkissue4879 messages
2009-02-03 09:08:56kristjan.jonssoncreate