IronPython 1.1.1 RC Released and DLR Hosting Spec
After a long hiatus there is a new release of IronPython 1.1: a release candidate of 1.1.1. If no problems are found this will shortly become 1.1.1.
The 1.1.1 release is a bugfix release, fixing around 20 bugs (most of which were already fixed in IronPython 2.0).
This is great news as IronPython 2.0 (the Dynamic Language Runtime based version) is still in alpha and a final release isn't expected until the end of the year. A lot of people (including Resolver Systems) are still using IronPython 1.1.
The hosting API for the DLR is still changing as it is adapted to better support multiple languages (especially IronRuby). The aim is to ship DLR 1.0 at the same time as IronPython 2.0 final (but that may not work out).
The goals for IronPython generally include CPython 2.5 compatibility and fully running on top of the DLR. There have already been numerous improvements from IronPython 1.1 -> 2.0 and there should be a bunch more random improvements (e.g. bug fixes, performance, etc…).
An updated DLR API hosting spec document was recently made available:
Not all of the functionality in the spec is avilable in the current release of the DLR (part of IronPython 2.0 Alpha 7).
The current status is that ScriptEngine, ScriptScope, ObjectOperations, and ScriptSource (but still named SourceUnit) are fully implemented – although there are certainly some bugs still lurking.
Current planning going forward is to work on replacing ScriptEnvironment w/ ScriptRuntime, switching to use MBRO objects instead of the interfaces used today (completing the remoting story), and other small tweaks. In February the team aim to be looking at finishing up the support for multiple engines in the same app domain, defining and implementing the full set of configuration/options, and general fit-and-finish work.
The 1.1.1 release is a bugfix release, fixing around 20 bugs (most of which were already fixed in IronPython 2.0).
This is great news as IronPython 2.0 (the Dynamic Language Runtime based version) is still in alpha and a final release isn't expected until the end of the year. A lot of people (including Resolver Systems) are still using IronPython 1.1.
The hosting API for the DLR is still changing as it is adapted to better support multiple languages (especially IronRuby). The aim is to ship DLR 1.0 at the same time as IronPython 2.0 final (but that may not work out).
The goals for IronPython generally include CPython 2.5 compatibility and fully running on top of the DLR. There have already been numerous improvements from IronPython 1.1 -> 2.0 and there should be a bunch more random improvements (e.g. bug fixes, performance, etc…).
An updated DLR API hosting spec document was recently made available:
Not all of the functionality in the spec is avilable in the current release of the DLR (part of IronPython 2.0 Alpha 7).
The current status is that ScriptEngine, ScriptScope, ObjectOperations, and ScriptSource (but still named SourceUnit) are fully implemented – although there are certainly some bugs still lurking.
Current planning going forward is to work on replacing ScriptEnvironment w/ ScriptRuntime, switching to use MBRO objects instead of the interfaces used today (completing the remoting story), and other small tweaks. In February the team aim to be looking at finishing up the support for multiple engines in the same app domain, defining and implementing the full set of configuration/options, and general fit-and-finish work.
Wow, that's cool.
ReplyDeleteI am trying to use DLR for my scripting language. It was hard for me to start using it.
So, I have created a simple solution with "minimal" language which consists of arithmetic expressions. You can find it here