bill janssen olchxynparccom theres really convoluted code socket_fileobject__init__ initializing _fileobject bufsize parameter explicitly given zero thats turned _rbufsize 1 combined min change produce readonebyte behavior code setting _rbufsize seems odd nice commented notes specific selections made bufsize 0 bufsize selfdefault_bufsize bufsize 0 self_rbufsize 1 elif bufsize 1 self_rbufsize selfdefault_bufsize else self_rbufsize bufsize self_wbufsize bufsize also depends whether read called explicit bytes read appears case code socketpy necessarily code opens socket likely library seems use bufsize zero httplib lot problems well think change cited imo correct affect number httpbased services well bill ralf terry right please file bug think may problem change dont time review depth hopefully others recall sockets reading one byte time problem recall bug 152 era windows bad back guido mon apr 14 2008 1025 terry reedy wrote ralf schmitt wrote message news932f8baf0804140912u54adc7d5md7261541857f21bdmailgmailcom hi im using mercurial release25maint branch noticed checking local repository takes 5 minutes around 30s ive tracked change httphgpydepyrelease25maintreve9446c6ab3cd svn revision 61009 diff inline alibsocketpy fri mar 23 142729 2007 0100 blibsocketpy sat feb 23 203059 2008 0100 3057 3057 self_rbuf true left size buf_len recv_size maxself_rbufsize left recv_size minself_rbufsize left data self_sockrecvrecv_size data break self_rbufsize 1 code reads one byte time clearly wrong im posting mailing list dont want issue get lost bugtracker least likely get lost mailing list new tracker items many devs subscribe _______________________________________________ pythondev mailing list zvlllneumpythonorg httpmailpythonorgmailmanlistinfopythondev unsubscribe httpmailpythonorgmailmanoptionspythondevpythondev40tangomucom thu 07 aug 2008 074450 0700 pythondev bad network performance