[IronPython] import socket fails on Win32
Martin.Maly at microsoft.com
Mon Nov 28 18:24:20 CET 2005
Keith's suggestion to use the .NET classes is a great way to use sockets from IronPython. Ideally we should be also able to import 'socket' into IronPython which means implementing the _socket as an IronPython built-in module or writing a wrapper that would allow IronPyton to call _python.pyd directly.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Boris Capitanu
Sent: Sunday, November 27, 2005 10:18 PM
To: users at lists.ironpython.com
Subject: [IronPython] import socket fails on Win32
First let me say Thank You for the wonderful job you guys have been doing so far with IronPython. I've been a long time user of Python.NET and have been very happy with the Python integration, with the only downside being that debugging is a little painfull when you can't step through the code or inspect variables. This is why I am now moving to IronPython.
Most of my code transitioned perfectly to IronPython, however I did reach one module that failed importing "socket" on a Windows platform.
I've traced the problem to a precompiled library in \Pyton24\DLLs folder, called _socket.pyd which is imported from \Python24\Lib\socket.py Apparently IronPython cannot handle the precompiled libraries yet. Any ideas on what needs to be done in order for this to work?
Thank you very much.
users mailing list
users at lists.ironpython.com
More information about the Ironpython-users