|
A rough road map here is that we plan to release small bug fix
releases (e.g. 1.0.1, 1.0.2) approximately every 6 weeks. Those releases
will big focused on fixing small non-destabilizing issues, high-priority
blocking issues w/ no work around, etc… We’ll then release 1.1 at some later point after we’ve
done some of those (likely after a beta and/or release candidate – but shorter
than the 1.0 cycle). 1.1 will include new some new features in addition
to larger bug fixes – that’s most likely where the improvements to
socket would come. From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Eric Larson Along these same lines, with
the 1.0 out how ofte can folks expect to see updates/patches? On 9/11/06, Dino Viehland <[EMAIL PROTECTED]>
wrote: 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). |
_______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
