"Paul Rubin" <http://[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > "Chris Tavares" <[EMAIL PROTECTED]> writes: > > Is this normal behavior for urllib? Is there a way to force that initial > > socket closed earlier? Is there something else I need to do? > > I'd say open a sourceforge bug. There may be a way around it with the > fancy opener methods of urllib2, but it's a bug if regular urllib > opens a second socket without closing the first one. For http 1.1 > it should be able to use just one socket anyway.
Thanks, I'll do some poking around in urllib first and see if I can narrow it down. Is there a way to do HTTP 1.1 with urllib? The docs say 0.9 and 1.0 only. Thanks, -Chris -- http://mail.python.org/mailman/listinfo/python-list
