Is "no registry module" _winreg or is it something else? The good news here might be that Srivatsn has implemented this for Beta 3 (along w/ cmath) but it didn't quite make it into b2.
Let us know if we end up pushing any bugs to statuses you don't like. BTW are all the bugs you've opened related to SCons or are some other issues? I'd also not mind seeing a bug calling for a dummy signal module :). And of course thanks for the update! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Hardy Sent: Friday, May 02, 2008 11:20 PM To: Discussion of IronPython; [EMAIL PROTECTED] Subject: [IronPython] SCons on IronPython 2.0B2 Hi all, SCons now 'works' on IronPython 2.0b2. I can compile a very simple C++ project, but there are a few caveats: * no registry module, so no tool detection. The SConscript needs to import the environment to find any tools. * Need a dummy signal module (attached) * Need a subprocess module (http://www.ironpython.info/index.php/The_subprocess_module) * There are a few small oddities, so the attached patch to SCons is required. Relevant IronPython bugs have been filed, of course :) I have opened SCons issue #2043 to track all of this. I hope I've included all of the details. The signal and subprocess modules need to be in the IronPython\Lib directory (or somewhere in IRONPYTHONPATH). Obviously, the Python 2.5 standard library must be available as well. I don't think the patch should be included in its current condition; I'm not 100% sure all the changes work with pure Python. It's pretty simple to block stuff off with sys.platform == 'cli', though. I'm going to try to push it a little harder now, but this is a good first start. -Jeff _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
