The latest sources also include some breaking changes to the Hosting API in the 
way the runtime and engine are initialized. So if your app is also a host, you 
would have to spend time fixing these changes. However, it probably isn't a lot 
of work to incorporate this change and this is something you would have to 
eventually do going forward.

Thanks
sesh

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Fugate
Sent: Wednesday, September 03, 2008 10:13 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Beta 4 or build from source?

Ipy.exe startup time took a ~60% hit a couple weeks ago which we're trying to 
get fixed before IP 2.0B5.  Also, there might be a few socket issues we're also 
in the process of fixing for Beta 5.

That said, there have been a huge number of bugs that have been fixed since 
Beta 4.

Dave

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dan Eloff
Sent: Wednesday, September 03, 2008 10:07 AM
To: Discussion of IronPython
Subject: [IronPython] Beta 4 or build from source?

Hi All,

Well the time has come again to upgrade to a newer version of
IronPython. I'm tempted to try one of the source code drops instead of
Beta 4,is there any reason I shouldn't use this morning's drop?

I'm happy to see that the performance of IronPython has been improving
constantly. Performance is key, I've upgraded my development PC twice,
and am running at a 20% overclock just to keep the edit, refresh,
debug cycles down to a reasonable amount of time. A large Silverlight
project takes a while to load in the browser :(

Incidentally bugs in psycopg2 drove me to create a ctypes client
library for PostgreSQL. This was my last remaining C library on the
backend, so I'm no longer tied to CPython. I eventually (early next
year) intend to compare IronPython on Mono to CPython 2.5 for running
the backend server, and choose the fastest of the two for final
testing and deployment. I expect I'll be pleasantly surprised by
IronPython.

-Dan
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

Reply via email to