Not addressing the import of python byte code, have you taken a look at .NET's TcpListener and TcpClient classes? I've grown rather fond of them in a recent project. Otherwise, some Python bytecode -> Python source -> IL path would need to happen. If the bytecode references a C-code Python dll, that would need some wrapper created (akin to a DllImport-attributed method in C#), which I don't think would be difficult to pull off. ----- Keith J. Farmer // [EMAIL PROTECTED]
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Boris Capitanu Sent: Sunday, 27 November 2005 22:18 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? _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
