[IronPython] Road to IronPython 2.7 (update)
dinov at microsoft.com
Tue Feb 22 03:48:16 CET 2011
Can you run w/ -X:ExceptionDetail? My guess is there's something different about Mono's big integer implementation when you do bigInt.ToString("X"). We used to convert the string to hex ourselves but that was slower than .NETs ToString implementation so I switched to using ToString instead (and uuid goes through this path).
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Tristan Zajonc
Sent: Monday, February 21, 2011 6:11 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Road to IronPython 2.7 (update)
There seems to be some regressions between 2.6 and 2.7 for OSX/Mono. In particular, in addition to the traceback bug, the uuid module still has a problem:
Given that uuid appears all over the place, this is relatively serious, I think. I'd look into these, but the standard IronPython solution doesn't compile on OSX/Mono.
On Mon, Feb 21, 2011 at 7:31 PM, Jimmy Schementi <jimmy at schementi.com<mailto:jimmy at schementi.com>> wrote:
I can do a quick test pass of the silverlight support.
On Mon, Feb 21, 2011 at 7:01 PM, Steve Dower <s.j.dower at gmail.com<mailto:s.j.dower at gmail.com>> wrote:
> The tools problem seems to be to do with the installer. IPyTools
> (PythonRuntimeHost.cs:89-100) tries to load the installed path from
> HKLM\SOFTWARE\IronPython\2.7\(default). On my machine (Win7 x64, IPy
> 2.7 RC1 installed without IPyTools, which were built from source) this
> is actually in HKLM\SOFTWARE\Wow6432Node\IronPython\2.7\(default)
> which contains "ipy64", which is then combined (PythonStarter.cs:69)
> with "ipy.exe" to make "ipy64\ipy.exe" as the interpreter path (which
> doesn't exist).
> If I set HKLM\SOFTWARE\Wow6432Node\IronPython\2.7\(default) to my
> actual install path (where ipy.exe is) it works fine. I assume this
> should be done in the installer.
> On Tue, Feb 22, 2011 at 10:12, Jeff Hardy <jdhardy at gmail.com<mailto:jdhardy at gmail.com>> wrote:
>> Hi all,
>> The following issues are blockers for IronPython 2.7:
>> * #29841 - sysconfig traceback when starting 2.7B1 -
>> I don't know enough about Mono/MacOS/POSIX to fix this one properly. I
>> haven't yet chercked what the Mono guys did to get it working on
>> * (no issue) - Visual Studio tools
>> The Visual Studio tools are basically broken right now - I can't
>> launch or debug even the default console program. I think it's because
>> it can't find the interpreter, but I thought I fixed that already.
>> * (no issue) - silverlight support
>> I have no idea what the status of the silverlight support is.
>> Once these are resolved (one way of another) I think 2.7 will be ready to go.
>> - Jeff
>> P.S. In all honesty I would have preferred to call the latest release
>> Beta 3 instead of RC1, but I had already changed the version strings
>> and didn't want to change them back :|.
>> Users mailing list
>> Users at lists.ironpython.com<mailto:Users at lists.ironpython.com>
> Users mailing list
> Users at lists.ironpython.com<mailto:Users at lists.ironpython.com>
Users mailing list
Users at lists.ironpython.com<mailto:Users at lists.ironpython.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironpython-users