Announcing IronPython 2.0.2
Hello Python Community,
I am delighted to announce the release of IronPython 2.0.2. This release is a
minor update to IronPython 2.0.1, which in turn is a CPython 2.5-compatible
release running on the .NET platform. Our priority was to make IronPython 2.0.2
a bugfix release that remains backwards-compatible with IronPython 2.0.1. In
particular, we focused on issues the IronPython community brought to our
attention through http://www.codeplex.com/. As such, there have been important
improvements on the compatibility and stability of IronPython as summarized
below.
You can download IronPython 2.0.2 at:
http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=22981
Silverlight users: A new version of Silverlight, specifically Silverlight 3, is
required to build the "Silverlight Release" or "Silverlight Debug"
configurations of IronPython.sln. Please update Silverlight accordingly if you
intend to do so.
Detailed change summary:
Fixed specifically for 2.0.2:
* 21577 - binascii.crc32 doesn't accept one argument.
* 20616 - wrong TypeError message when invoking "str.join": implicit
parameter 'self' not counted
* 19665 - 2.0.2: operator.isSequenceType(NewStyleClass) broken
* 20087 - 2.0.2: Null Value Exception in COM interop
* 21445 - DLR: There is a dead loop in CallSite.UpdateAndExecute(),
which leads to IronPython 2.0.1 hang.
* 22001 - 2.0.2: Ngen IronPython.msi option doesn't work on 64-bit
platforms?
* 22094 - 2.0.2: StringException leaked to Python via sys.exc_info()
* 22239 - 2.0.2: modules aren't isolated
Backported 2.6 fixes:
* 20634 - hex_codec needs to be imported before hex decode can happen
* 20302 - codecs.lookup errors with uppercase encoding names
* 20051 - Re-raising exception causes loss of traceback
* 4565 - Support all encodings CPython does for _codecs.encode and
_codecs.decode
* 20603 - os.walk('') doesn't work
* 21929 - os.listdir does not accept empty path
* 17235 - dir(System.ArgIterator) broken
I would especially like to thank adamilan, dungen, fuzzyman, hfoffani,
hhonisch, kuno, orestis, sanxiyn, and tkamiya for raising these issues. By
taking the time to share their insights, these CodePlex users have brought
about tangible improvements in the quality of IronPython. Keep those bug
reports coming!
- The IronPython Team
--
http://mail.python.org/mailman/listinfo/python-announce-list
Support the Python Software Foundation:
http://www.python.org/psf/donations/
Announcing IronPython 2.0.3
Hello Python Community, I am delighted to announce the release of IronPython 2.0.3. This release 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 http://www.codeplex.com/. As such, there have been important improvements on the compatibility and stability of IronPython as summarized below. You can download IronPython 2.0.3 at: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=30416 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 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 bringing these issues to our attention. Thanks for spending the time and effort that allows us to continue improving IronPython! - The IronPython Team -- http://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
Announcing IronPython 2.6.1 RC1
Hello Python Community, We're pleased to announce the release of IronPython 2.6.1 RC1. This version of IronPython makes great strides in stability and compatibility, including a considerable number of targeted bugfixes. Because this is our largest servicing release to date, and due to our decision against incrementing the assembly version numbers, it is important that we get everything right. To this end, we present our first-ever RC for a minor dot release. Of course, your feedback is imperative to the quality of this release, so we'd love to hear from you! IronPython 2.6.1 comes in two flavors - one that runs on top of .NET 4.0 RC, and one that runs on any other framework starting with .NET 2.0 SP1. They can be downloaded here: - IronPython 2.6.1 RC1 for .NET 2.0 SP1: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=40144 - IronPython 2.6.1 RC1 for .NET 4.0 RC: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=40146 Note: The .NET Framework 4.0 RC is required for the latter release and can be downloaded at http://www.microsoft.com/downloads/details.aspx?FamilyID=a9ef9a95-58d2-4e51-a4b7-bea3cc6962cb&displaylang=en IronPython 2.6.1 RC1 includes fixes for well over 50 bugs, large and small. Ctypes has had a number of significant updates, including union support, variant_bool, and wintypes. Another focus has been on sys.settrace, making debugging more reliable. For example, sys.settrace now returns the correct frame, supports tracing through modules, and no longer interferes with "import os". Other notable fixes include thread-safe importing, and the missing error code in _winreg exception. In addition, we've made a substantial improvement in import time. Not only does this reduce startup time, but can speed up the importing of large, definition-heavy modules by up to 50%. As you might imagine, the .NET 4.0 flavor of IronPython 2.6.1 RC1 has a few of its own changes designed for better interoperability with the framework. These include fixing some errors with Func<> and better runtime isolation when similarly-named assemblies in different locations are loaded in multiple engines. In addition, both the .NET 2.0 and .NET 4.0 builds support the new .NET 4.0 IStructuralEquatable and IStructuralComparable interfaces and maps them to the appropriate operations (__eq__, __hash__, __gt__, etc.). In the case of .NET 4.0, this replaces IValueEquality as the gold standard for defining equality in an interop-friendly manner. In the .NET 2.0 build, these interfaces are copied so that their use can be phased in while retaining IValueEquality for backwards compatibility. Special thanks to Albert Szilvasy, cendalc, clovery, egonw_, essey, fabiofz, igalse, jazzcat, jlunder, laughingboy, marten_range, László de Almásy, lbaker, Lukas Cenovsky, pl6306, roinet, sanxiyn, Thomas Heller, vernondcole, and Wolfram for reporting issues. Happy Scripting! - The IronPython Team -- http://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
Announcing IronPython 2.6.1
Hello Python Community, We're pleased to announce the final release of IronPython 2.6.1. This version of IronPython makes great strides in stability and compatibility, including a considerable number of targeted bugfixes. This is our largest servicing release to date, and with your help both before and during the RC phase, along with the simultaneous release of .NET 4.0, this has become a very exciting release for all of us. IronPython 2.6.1 comes in two flavors - one that runs on top of .NET 4.0, and one that runs on any earlier framework starting with .NET 2.0 SP1. They can both be downloaded at http://ironpython.codeplex.com/releases/view/36280. We'd like to place a particular emphasis on the .NET 4.0 flavor of IronPython 2.6.1 and encourage all of you to try it out. It has a number of advantages over the 2.0 version, some of which Dave discusses on his blog at http://knowbody.livejournal.com/20751.html. These include faster startup time, compatibility with C#'s new dynamic keyword, and access to the numerous new features present in the updated Framework. The final release of Microsoft .NET Framework 4.0 is publically available as of today, and is required for this flavor of IronPython 2.6.1. Download it here: http://www.microsoft.com/downloads/details.aspx?FamilyID=9cfb2d51-5ff4-4491-b0e5-b386f32c0992&displaylang=en The IronPython 2.6.1 RC included fixes for well over 50 bugs, large and small. Ctypes has had a number of significant updates, including union support, variant_bool, and wintypes. Another focus has been on sys.settrace, making debugging more reliable. For example, sys.settrace now returns the correct frame, supports tracing through modules, and no longer interferes with "import os". Other notable fixes include thread-safe importing, and the missing error code in _winreg exception. In addition, we've made a substantial improvement in import time. Not only does this reduce startup time, but it can speed up the importing of large, definition-heavy modules by up to 50%. As you might imagine, the .NET 4.0 flavor of IronPython 2.6.1 RC has a few of its own changes designed for better interoperability with the framework. These include fixing some errors with Func<> and better runtime isolation when similarly-named assemblies in different locations are loaded in multiple engines. In addition, both the .NET 2.0 and .NET 4.0 builds support the new .NET 4.0 IStructuralEquatable and IStructuralComparable interfaces and maps them to the appropriate operations (__eq__, __hash__, __gt__, etc.). In the case of .NET 4.0, this replaces IValueEquality as the gold standard for defining equality in an interop-friendly manner. In the .NET 2.0 build, these interfaces are copied so that their use can be phased in while retaining IValueEquality for backwards compatibility. Since the RC, we have fixed numerous other issues, as well as adding CPython's ssl.py to our distribution. We've also made some major unicode-related changes in response to your feedback on the mailing list, changes that improve compatibility with certain third-party applications including Django. In particular, invoking unicode() or using unicode string formatting will now call __unicode__() first if it is present on the object. Finally, we've included a new code sample that shows how to use __clrtype__ to create custom CLR classes from IronPython. This sample is a sneak preview of what we expect will become a fully supported IronPython module, so we encourage anyone who is so inclined to try it out and let us know how it goes. Special thanks to Albert Szilvasy, amajorek, cendalc, clovery, egonw_, Eloff, essey, fabiofz, gjones, gpgemini, Haibo Luo, igalse, jazzcat, jdhardy, jlunder, JustinCle, klrohe, László de Almásy, laughingboy, lbaker, Lukas Cenovsky, marten_range, olav, paulfelix, pl6306, razam, roinet, russomf, sanxiyn, see_toronto web de, Thomas Heller, variant77, vernondcole, William Reade, and Wolfram for reporting issues and making this a great release. Happy scripting! - The IronPython Team -- http://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
