> Originally we were trying to implement "_socket" instead of "socket". We > ran into one problem with this: the standard socket.py module has an > implicit dependency upon CPython's reference counting garbage collector > (for implementing dup). We considered a hack to make this work but > ultimately rejected it in favor of implementing "socket" instead replacing > the standard Python module. Unfortunately makefile didn't make it - and > that looks like the same thing for ssl (it's present in CPythons socket > but not _socket). > > Select was a much simpler case of just not getting to it in time. We'll > ship a select implementation w/ the 1.1 release - we'll need to look at > makefile & ssl though (makefile should be trivial, hopefully ssl will be > just as trivial).
I cannot deny that would be fantastic to have a complete implementation of the socket module. ssl would then be the cherry on top of it ;) Thanks for the feedback - Sylvain > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sanghyeon Seo > Sent: Monday, September 11, 2006 3:17 AM > To: [EMAIL PROTECTED]; Discussion of IronPython > Subject: Re: [IronPython] socket for IronPython update > > 2006/9/11, Sylvain Hellegouarch <[EMAIL PROTECTED]>: >> Thanks a lot Seo. >> >> Any reason that I would have missed why the built-in socket module >> does not include those missing module functions? > > Well, that question should be answered by IronPython team, not me. > > I think the reason is... well, because they haven't got a time to > implement them. > > Seo Sanghyeon > _______________________________________________ > 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
