[IronPython] IronPython 2.0 RC 2 on Mono

2008-12-07 Thread Seo Sanghyeon
Currently you need Mono SVN (both to run and to compile). Using SVN r120972 below. The binary runs fine. IronPython includes its own copy of ExtensionAttribute, but this doesn't seem to work with Mono C# compiler: that is, extension methods don't get recognized as extension methods. This causes t

Re: [IronPython] Last source drop was Nov 30. Is something broken?

2008-12-07 Thread Dan Eloff
On Sun, Dec 7, 2008 at 2:02 PM, Dino Viehland <[EMAIL PROTECTED]> wrote: > Something went wrong on the machine that pushes the source code out and then > there were some changes that required the script to be updated. It's working > now and pushed out an update yesterday. > Excellent. *rubs han

[IronPython] Unused files

2008-12-07 Thread Seo Sanghyeon
Following files seem to be unused but are included in 2.0 RC2 source. Please remove them before the final release... Microsoft.Scripting.Core/Actions/RestrictedMetaObject.cs Microsoft.Scripting.Core/Ast/ExpressionTreeVisitor.Generated.cs Microsoft.Scripting.Core/Ast/LabeledStatement.cs Microsoft.S

Re: [IronPython] Last source drop was Nov 30. Is something broken?

2008-12-07 Thread Dino Viehland
Something went wrong on the machine that pushes the source code out and then there were some changes that required the script to be updated. It's working now and pushed out an update yesterday. > -Original Message- > From: [EMAIL PROTECTED] [mailto:users- > [EMAIL PROTECTED] On Behalf O

Re: [IronPython] NWSGI 0.7 released

2008-12-07 Thread Miha Valencic
Thanks for the info. Miha 2008/12/6 Jeff Hardy <[EMAIL PROTECTED]> > Hi Miha, > As Dan said, there are issues with str == unicode (although there is a > [...] ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/us

Re: [IronPython] CP #20099: Stack Overflow using super() in dict subclass

2008-12-07 Thread Jeff Hardy
On Sat, Dec 6, 2008 at 2:16 PM, Dino Viehland <[EMAIL PROTECTED]> wrote: > The immediate question would be does fixing this unblock all other Django > issues? If there's going to be a long tail of other bugs then it'd be better > to just fix them all for 2.0.1. I doubt it, if past experience is