Incomplete. Many of the builtin modules are not yet implemented. It is
going to be the focus of our work between now and 1.0 to implement more
and more of those.
Martin
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On
> Behalf Of Chu Kevin
> Sent: Friday, Au
I agree that wait IronPython release 1.0,and begin work for std lib.
But I wonder which lib need to port? or which level lib need to port?
ex:_socket module or socket.py or SocketServer.py ?
I think _socket is Low-level module write-by C,but socket.py invoke
_socket,so we just need to implement
Kevin,
I agree with your suggestion to create a new gotdotnet group for
porting the std library packages, but only if the ironpython folks are
not going to do it. I have recently sent an email to Jim to get some
clarity on their plans on this issue, and I prefer to wait just a
little bit longer to
I suggest create project ".NET port of Python standard lib" in
gotdotnet workspace
and I can join this work.
2005/8/6, Anthony Tarlano <[EMAIL PROTECTED]>:
> Kevin,
>
> Incomplete, would be the answer to your question. Currently,
> IronPython doesn't come with batteries include (python std librar
Kevin,
Incomplete, would be the answer to your question. Currently,
IronPython doesn't come with batteries include (python std libraries).
I am actively thinking about creating an effort to complete this part
of the puzzel and port all the python standard library interfaces to
.NET with community
