Isn't that what Seo's Community Edition is for? Obviously not the official MSFT edition, but it certainly does the trick.<br><br><div><span class="gmail_quote">On 9/15/06, <b class="gmail_sendername">J. Merrill</b> <<a href="mailto:jvm_cop@spamcop.net">
jvm_cop@spamcop.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Sorry, I wasn't clear. I was referring to this for
1.1. Or are you saying that some part of the licensing / legalistic stuff that goes on (invisibly to many of us) means that you can't put any "outsider contributions" into what you ship?<br><br>At 01:02 PM 9/15/2006, Dino Viehland wrote
<br>>Unfortunately we cannot currently accept changes back into the IronPython core right now. :(<br>><br>>-----Original Message-----<br>>From: <a href="mailto:users-bounces@lists.ironpython.com">users-bounces@lists.ironpython.com
</a> [mailto:<a href="mailto:users-bounces@lists.ironpython.com">users-bounces@lists.ironpython.com</a>] On Behalf Of J. Merrill<br>>Sent: Friday, September 15, 2006 9:58 AM<br>>To: Discussion of IronPython<br>>Subject: Re: [IronPython] socket for IronPython update
<br>><br>>Is there a reason not to pick up Seo's version? His "license" ("do whatever ... you want") would certainly allow it. Is the wheel he built not round enough?<br>><br>>At 11:40 AM 9/11/2006, Dino Viehland wrote
<br>>>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).
<br>>><br>>>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).
<br><br><br>J. Merrill / Analytical Software Corp<br><br><br>_______________________________________________<br>users mailing list<br><a href="mailto:users@lists.ironpython.com">users@lists.ironpython.com</a><br><a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com">
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a><br></blockquote></div><br><br clear="all"><br>-- <br>/M:D<br><br>M. David Peterson<br><a href="http://mdavid.name">http://mdavid.name</a> | <a href="http://www.oreillynet.com/pub/au/2354">
http://www.oreillynet.com/pub/au/2354</a>