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:14:58
SpamBayes Score 3.9793317e-08
Marked as misclassified No
Message-id <>
I'm afraid I misunderstood the problem.
Yes, since u.fp is now a io.BufferedReader() rather than a socket.Socket
(), the _sock member has moved.

But looking at the other assertions in, you can see 
the different ways the code uses to get at the socket:  There is 
u.fp.raw._sock and there is u.fp.fp.raw._sock.

IMHO I think we have to assume the _sock member to be an implementation 
detail that is not part of the interface.
Date User Action Args
2009-02-03 09:14:59kristjan.jonssonsetrecipients: + kristjan.jonsson, amaury.forgeotdarc, pitrou, benjamin.peterson
2009-02-03 09:14:59kristjan.jonssonsetmessageid: <>
2009-02-03 09:14:59kristjan.jonssonlinkissue4879 messages
2009-02-03 09:14:58kristjan.jonssoncreate