t; Sent: Friday, August 05, 2005 7:37 PM
> To: Discussion of IronPython
> Subject: [IronPython] Python Lib Socket
>
> >>> import SocketServer
> IronPython.Objects.PythonImportError: No module named _socket
>at socket.Initialize() in
> F:\Tech\Python\IronPy
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
>>> import SocketServer
IronPython.Objects.PythonImportError: No module named _socket
at socket.Initialize() in F:\Tech\Python\IronPython-0.9\bin\Lib\socket.py:lin
e 45
at SocketServer.Initialize() in F:\Tech\Python\IronPython-0.9\bin\Lib\SocketS
erver.py:line 132
at input_5.Run(Frame fram
