: this version of IronPython is for .NET Framework 2.0 SP1, 3.0 and 3.5. If you want a version of IronPython to work on .NET Framework 4.0 with C# 4.0's new "dynamic" keyword, you need a compatible version of IronPython. As of this release, IronPython for .NET Framework 4.0 Beta 2
is the most current .NET 4.0 compatible version.
IronPython 2.0.3 is a minor update to IronPython 2.0.2 and the latest in a series of CPython 2.5-compatible releases running on the .NET platform. Again, our priority was to make IronPython 2.0.3 a bugfix release that remains backwards-compatible with IronPython 2.0.2. In particular, we focused on issues the IronPython community brought to our attention through CodePlex. As such, there have been important improvements on the compatibility and stability of IronPython as summarized below.
Silverlight users: As of IronPython 2.0.2, a new version of Silverlight, namely Silverlight 3, is required to build the “Silverlight Release” and “Silverlight Debug” configurations of IronPython.sln. Please update Silverlight accordingly if you intend to do so.
The following issues were fixed:
- 24224 – UTF-8 encoding sometimes broken!
- 19510 – Need to recognize DefaultMemberAttribute for getitem/setitem
- 24129 – 2.0.3: not <object-with-len-returning-nonzero> should not be 1
- 21976 – 2.0.3: Executables created by Pyc.py broken without access to original Python sources
- 24452 – 2.0: Fix FxCop warnings
- 24453 – 2.0: Cannot build “FxCop” build configuration of IronPython.Modules.csproj
- 24571 – 2.0.3: help(Array[Int32]) causes a traceback
- 24373 – empty sys.argv in compiled scripts for 2.0
- 24475 – Creating a low-permission version of PythonEngine fails post 2.0.0
- An issue where sys.argv lacks its first argument (the executable name) in compiled scripts
- A failure in partial trust on Windows 7 due to a SecurityException.
Special thanks goes out to kanryu, fwereade, kuno, kylehr, and Vassi for reporting these issues.