D] On Behalf Of Jeff Hardy
Sent: Monday, May 05, 2008 4:50 PM
To: Discussion of IronPython
Subject: Re: [IronPython] SCons on IronPython 2.0B2
Hi Dino,
Thanks for all the information! I find it helpful when filing bugs to
know how the team prioritizes bugs, what they look for, etc. It makes
it eas
Future. Those are bugs we don't think we can get to anytime
> soon due to deep architectural issues. If something's been moved to 2.1 then
> it's more the case that we think this can wait and that's an easy decision to
> reverse.
>
>
> -Original Message-
>
think this can wait and that's an easy decision to
reverse.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Hardy
Sent: Saturday, May 03, 2008 12:40 AM
To: Discussion of IronPython
Subject: Re: [IronPython] SCons on IronPython 2.0B2
Hi Dino,
Yea
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 ar
iday, 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 SConsc
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
(h
