This project has moved and is read-only. For the latest updates, please go here.

2.0 Beta 4

Rating: No reviews yet
Downloads: 5600
Released: Aug 5, 2008
Updated: Nov 10, 2009 by dfugate
Dev status: Beta Help Icon

Recommended Download

Application IronPython-2.0B4.msi
application, 4357K, uploaded Aug 6, 2008 - 2859 downloads

Other Available Downloads

application, 1992K, uploaded Aug 6, 2008 - 978 downloads
Source Code
source code, 2785K, uploaded Aug 6, 2008 - 790 downloads
example, 10K, uploaded Aug 7, 2008 - 973 downloads

Release Notes

I’m pleased to announce IronPython 2.0 Beta4. We have fixed around 50 bugs(~45 of them reported on Codeplex and ~5 reported internally). Apart from these bug fixes, the following are the highlights of this release:
  • This release ships with a MSI installer that installs IronPython along with the Python Standard Library. It is now dual-licensed with IronPython shipping under MS-PL and the python standard library shipping under the Python Software Foundation license. This means that existing python libraries are readily available after installation and makes for a better out-of-the-box experience of using existing CPython libraries. A zip file containing the binaries is still available as before.
  • Static compilation of python files is now supported again and the sample has been updated to use the newer version.
  • IDispatch-based cominterop is now the default mode as opposed to generating interop assemblies for interacting with COM components. This is a change that might break some existing scripts. One can switch back to the old behavior by setting the environment variable COREDLR_PreferComInteropAssembly. Read this blog for more details on this feature.
  • Apart from the Silverlight binaries and Chiron, the templates and tools to create a barebones app are included as well. This is in the Silverlight\Script folder.
  • Performance degrades that were reported in Beta 3 have been fixed.
  • As mentioned previously in the mailing list, IronPython now requires .NET 2.0 SP1. This is so that the DLR can make use of some fixes that are present in .NET 2.0 SP1

Reviews for this release

No reviews yet for this release.