[IronPython] FePy status update
Now I updated FePy's NAnt build file to include newly introduced Microsoft.System.Debugging.dll. I also found that I need to define CLR2 symbol to compile Microsoft.Dynamic.dll. Without the symbol it won't compile. What is the purpose of this symbol? Sorry for the delay, -- Seo Sanghyeon ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] FePy status update
We recently made the call that Microsoft.Dynamic's API surface would ship in .NET 4 as all internal API surface. It's still open source so anyone can pick it up and include it in their own languages to get COM support but C# needs it in the box somewhere so they can provide COM support as well. But we're not really sure what we want .NET COM support to look like long term yet so we don't want to commit to shipping the API forever just yet. The CLR2 flag allows us to build it as publicly accessible APIs on .NET 2/3/3.5 and build it as internal APIs in our internal builds for .NET 4. From: users-boun...@lists.ironpython.com [users-boun...@lists.ironpython.com] on behalf of Seo Sanghyeon [sanx...@gmail.com] Sent: Wednesday, July 15, 2009 2:43 AM To: Discussion of IronPython Subject: [IronPython] FePy status update Now I updated FePy's NAnt build file to include newly introduced Microsoft.System.Debugging.dll. I also found that I need to define CLR2 symbol to compile Microsoft.Dynamic.dll. Without the symbol it won't compile. What is the purpose of this symbol? Sorry for the delay, -- Seo Sanghyeon ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] FePy status update
On #4 I'm going to check-in the fix today - sorry for the delay! -Original Message- From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Seo Sanghyeon Sent: Saturday, May 09, 2009 3:05 AM To: Discussion of IronPython Subject: [IronPython] FePy status update FePy seems to be dead, right? Sorry about that. This is a brief status update. And I could use it later as a changelog. How convinient. 1. I am now testing IronPython with CPython 2.6 standard library. FePy used 2.4 so far. Be sure to check collections.py issue Dave mentions here: http://knowbody.livejournal.com/13271.html 2. NAnt build system has been updated to the latest source layout change. My goal still is to do away with NAnt and improve Mono's implementation of MSBuild to build IronPython out of the box, but that hasn't progressed a bit, sorry. Dave wrote about the source layout change here: http://knowbody.livejournal.com/13980.html 3. ExtensionAttribute problem mentioned in the last December is gone. Mono bug on reference equality with generic constraints mentioned in March is still there. FePy trunk patches/latest has a workaround for this. Net result is that latest IronPython source drops from CodePlex compiles and runs with Mono! And no compiler warnings! (This has been my pet peeve, you know.) And I had no problem keeping it that way for some time. I updated IronPython on Mono reports page with relevant mails. http://fepy.sourceforge.net/doc/ironpython-mono-report.html 4. There is an IronPython bug that manifests only on Mono due to newline difference. The symptom is that expressions are not printed in interactive console. This took some time to debug, but there is a fix now. http://lists.ironpython.com/pipermail/users-ironpython.com/2009-April/010140.html 5. Current build on my local system generally works. It imports urllib and urllib2. This is quite a stress test... Not just import, but downloading webpages work too. On the other hand, importing decimal crashes Mono in segmentation fault! I suspect this has to do with move to 2.6 standard library and its abstract base classes meta machineries, but who knows. -- Seo Sanghyeon ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
[IronPython] FePy status update
FePy seems to be dead, right? Sorry about that. This is a brief status update. And I could use it later as a changelog. How convinient. 1. I am now testing IronPython with CPython 2.6 standard library. FePy used 2.4 so far. Be sure to check collections.py issue Dave mentions here: http://knowbody.livejournal.com/13271.html 2. NAnt build system has been updated to the latest source layout change. My goal still is to do away with NAnt and improve Mono's implementation of MSBuild to build IronPython out of the box, but that hasn't progressed a bit, sorry. Dave wrote about the source layout change here: http://knowbody.livejournal.com/13980.html 3. ExtensionAttribute problem mentioned in the last December is gone. Mono bug on reference equality with generic constraints mentioned in March is still there. FePy trunk patches/latest has a workaround for this. Net result is that latest IronPython source drops from CodePlex compiles and runs with Mono! And no compiler warnings! (This has been my pet peeve, you know.) And I had no problem keeping it that way for some time. I updated IronPython on Mono reports page with relevant mails. http://fepy.sourceforge.net/doc/ironpython-mono-report.html 4. There is an IronPython bug that manifests only on Mono due to newline difference. The symptom is that expressions are not printed in interactive console. This took some time to debug, but there is a fix now. http://lists.ironpython.com/pipermail/users-ironpython.com/2009-April/010140.html 5. Current build on my local system generally works. It imports urllib and urllib2. This is quite a stress test... Not just import, but downloading webpages work too. On the other hand, importing decimal crashes Mono in segmentation fault! I suspect this has to do with move to 2.6 standard library and its abstract base classes meta machineries, but who knows. -- Seo Sanghyeon ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] FePy status update
Hey Seo, On 5/9/09, Seo Sanghyeon sanx...@gmail.com wrote: 4. There is an IronPython bug that manifests only on Mono due to newline difference. The symptom is that expressions are not printed in interactive console. This took some time to debug, but there is a fix now. http://lists.ironpython.com/pipermail/users-ironpython.com/2009-April/010140.html Fwiw, I reported it on ironruby-core weeks ago: http://rubyforge.org/pipermail/ironruby-core/2009-March/004008.html Along with a patch. -- Jb Evain j...@nurv.fr ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] FePy status update
2009/5/9 Jb Evain j...@nurv.fr: Hey Seo, On 5/9/09, Seo Sanghyeon sanx...@gmail.com wrote: 4. There is an IronPython bug that manifests only on Mono due to newline difference. The symptom is that expressions are not printed in interactive console. This took some time to debug, but there is a fix now. http://lists.ironpython.com/pipermail/users-ironpython.com/2009-April/010140.html Fwiw, I reported it on ironruby-core weeks ago: http://rubyforge.org/pipermail/ironruby-core/2009-March/004008.html Along with a patch. Oops, how did I miss that. Apparently this was to be fixed see http://rubyforge.org/pipermail/ironruby-core/2009-March/004089.html but somehow slipped for 2 months... -- Seo Sanghyeon ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] FePy status update
2009/5/9 Seo Sanghyeon sanx...@gmail.com: 2009/5/9 Jb Evain j...@nurv.fr: Hey Seo, On 5/9/09, Seo Sanghyeon sanx...@gmail.com wrote: 4. There is an IronPython bug that manifests only on Mono due to newline difference. The symptom is that expressions are not printed in interactive console. This took some time to debug, but there is a fix now. http://lists.ironpython.com/pipermail/users-ironpython.com/2009-April/010140.html Fwiw, I reported it on ironruby-core weeks ago: http://rubyforge.org/pipermail/ironruby-core/2009-March/004008.html Along with a patch. Oops, how did I miss that. Apparently this was to be fixed see http://rubyforge.org/pipermail/ironruby-core/2009-March/004089.html but somehow slipped for 2 months... I filed an issue against DLR, please vote: http://dlr.codeplex.com/WorkItem/View.aspx?WorkItemId=3010 -- Seo Sanghyeon ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] FePy status update
This is great news. Naturally we are all on tenterhooks waiting for a FePy release targeting IronPython 2.0.1 - even if it requires Mono 2.4. :-) All the best, Michael Seo Sanghyeon wrote: FePy seems to be dead, right? Sorry about that. This is a brief status update. And I could use it later as a changelog. How convinient. 1. I am now testing IronPython with CPython 2.6 standard library. FePy used 2.4 so far. Be sure to check collections.py issue Dave mentions here: http://knowbody.livejournal.com/13271.html 2. NAnt build system has been updated to the latest source layout change. My goal still is to do away with NAnt and improve Mono's implementation of MSBuild to build IronPython out of the box, but that hasn't progressed a bit, sorry. Dave wrote about the source layout change here: http://knowbody.livejournal.com/13980.html 3. ExtensionAttribute problem mentioned in the last December is gone. Mono bug on reference equality with generic constraints mentioned in March is still there. FePy trunk patches/latest has a workaround for this. Net result is that latest IronPython source drops from CodePlex compiles and runs with Mono! And no compiler warnings! (This has been my pet peeve, you know.) And I had no problem keeping it that way for some time. I updated IronPython on Mono reports page with relevant mails. http://fepy.sourceforge.net/doc/ironpython-mono-report.html 4. There is an IronPython bug that manifests only on Mono due to newline difference. The symptom is that expressions are not printed in interactive console. This took some time to debug, but there is a fix now. http://lists.ironpython.com/pipermail/users-ironpython.com/2009-April/010140.html 5. Current build on my local system generally works. It imports urllib and urllib2. This is quite a stress test... Not just import, but downloading webpages work too. On the other hand, importing decimal crashes Mono in segmentation fault! I suspect this has to do with move to 2.6 standard library and its abstract base classes meta machineries, but who knows. -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
