No need. It hasn't been verified as Fixed yet, and I should be getting to this particular bug next week. Looks like you've probably even saved me a bit of investigative time for proving this can't be closed so thanks:)
Dave -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael Foord Sent: Saturday, November 21, 2009 7:59 AM To: Discussion of IronPython Subject: Re: [IronPython] [ANN]: IronPython 2.6 Release Candidate 3 Dave Fugate wrote: > Hi Michael, glancing over the source history it appears as if > _codecs.lookup_error has been disabled under Silverlight forever and is not a > regression from IronPython 2.0. That said, it might turn out this falls > under the umbrella of > http://ironpython.codeplex.com/WorkItem/View.aspx?WorkItemId=17383, and is > something we can address for 2.6.1. > > That issue is closed, shall I open a new one? Michael > Thanks, > > Dave > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Michael Foord > Sent: Friday, November 20, 2009 4:01 PM > To: Discussion of IronPython > Subject: Re: [IronPython] [ANN]: IronPython 2.6 Release Candidate 3 > > Dave Fugate wrote: > >> 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. >> >> > Any chance the _codecs issue I mentioned is fixed in Release Candidate > 3? It blocks me using the standard library json module (simplejson) in > Silverlight so is a major PITA. > > Michael > > > >> 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 >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com >> >> > > > -- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
