This is a great analysis - based upon this I think it'll be pretty easy to fix 
this.  I'll take a look at it tomorrow and respond back.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher
Sent: Monday, February 18, 2008 4:19 PM
To: Discussion of IronPython
Subject: Re: [IronPython] urllib.urlretrieve with IronPython 2a8

On Feb 18, 2008 4:12 PM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote:
>
> Is it possible that CPython's socket.close method won't actually close
> the socket while there's still a makefile'd file attacked to the
> underlying OS socket?  And that IronPython's will?  Because that's the
> only explanation I can come up with.

It is and it will.  CPython basically dups the socket handle when you
call makefile, while IronPython does not.  That's the cause of this
bug.

By the way, the docstring for the IronPython socket class claims that
makefile isn't implemented.  This is apparently only half-true. :P

--
Curt Hagenlocher
[EMAIL PROTECTED]
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

Reply via email to