[IronPython] [ANN]: IronPython 2.6 Release Candidate 3
Jimmy.Schementi at microsoft.com
Sat Nov 21 14:49:38 CET 2009
Yes, it’s certain that the hosting APIs will not ship in .NET 4. Basically everything that is in Microsoft.Scripting.Core.dll is what has made its way into .NET 4.0. Sorry if that wasn’t clear.
You’ll also notice that Microsoft.Scripting.dll has been split into Microsoft.Scripting.dll and Microsoft.Dynamic.dll; the hosting APIs are still contained in Microsoft.Scripting.dll, while the things language implementers need to care about is in Microsoft.Dynamic.dll. We’re trying to not change Microsoft.Scripting.dll as much as possible, as those APIs have undergone some rigorous design and reviews. Microsoft.Dynamic.dll definitely will change.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Keith J. Farmer
Sent: Saturday, November 21, 2009 2:56 AM
To: Discussion of IronPython; python-announce-list at python.org
Subject: Re: [IronPython] [ANN]: IronPython 2.6 Release Candidate 3
Hey, Dave.. Based on Dino’s presentation at PDC, is it therefore certain that the hosting APIs will *not* ship as part of .NET 4? Has there been any official word as to support of those APIs in that event?
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Dave Fugate
Sent: Friday, November 20, 2009 9:54 AM
To: users at lists.ironpython.com; python-announce-list at python.org
Subject: [IronPython] [ANN]: IronPython 2.6 Release Candidate 3
Hello Python Community,
We’re pleased to announce the third and hopefully final release candidate of IronPython 2.6 which can be downloaded at http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=36150. Release Candidate 3 only includes Silverlight-related changes pertaining to some incompatibilities between 2.6 RC1 and RC2. Those who utilize IronPython for non-Silverlight scenarios will happily find virtually no churn from RC2. We strongly encourage everyone interested in Silverlight to test out this release ASAP because we plan on releasing IronPython 2.6 final in a week if no major new regressions are detected.
Thanks to everyone in the IronPython Community who reported bugs and provided valuable feedback: Zachc, yamakox, vernondcole, VAks, tscottw, tonyandrewmeyer, tomwright, TomasMatousek, tkamiya, timers, srivatsn, sopeajw, saveenr, sanxiyn, rridge, ronniemaor, quirogaco, pythonfoo, py_sunil, pm100, pl6306, paulfelix, orestis, olegt, oldman, NDHUMuscle, mycall, mmaly, mmacdonaldssfcu, maplpro, luntain, llaske, lbaker, Lawouach, laurionb, laughingboy, kurhan, kuno, kowenswp, klrohe, kevgu, jmesserly, jlunder, jdhardy, jbevain, jackeyoo, hhonisch, gz, gjones, fwereade, deadalusai, daveremy, CurtHagenlocher, chaghi, cgravill, cartman, bobarnso, atifaziz, ashcor, alvanet, __Helmut__, fuzzyman, fabiofz, Eloff, egonw_, dungen, dsblank, and dmajnemer.
Thank you for your continued support of IronPython.
The IronPython Team
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users