Re: [IronPython] Announcing IronPython 2.6 Alpha 1
Hopefully the approval is speedy. The other parts of ASP.Net Futures 2007 source code have been made available last month http://aspnet.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=25804 On Wed, May 6, 2009 at 7:26 AM, Adam Brand ad...@silverkeytech.com wrote: That is great news, and a great solution! Thanks! Adam *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Jimmy Schementi *Sent:* Tuesday, May 05, 2009 9:25 PM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Rather than just releasing builds, I’m waiting on the OK from the ASP.NETto release to source code for it, so it can be included in the IronPython releases and the Codeplex sources/daily builds. That seems like a much better solution. =) I’ll keep you posted (I’ve been in conference-mode for the past couple months, so things have been slow, sorry!). *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Adam Brand *Sent:* Tuesday, May 05, 2009 5:39 PM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any updated timeline on this (IronPython 2.6/ASP.Net Integration)? Just wanted to check in and see where it was on the list. Thanks, Adam 2009/3/30 Jimmy Schementi jimmy.scheme...@microsoft.com A IronPython 2.6 version of the ASP.NET integration will be out shortly, I have to get time to make a build and get it sent over to the ASP.NET team. I’m working through some other things I need to get done first, but assume two weeks. *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Adam Brand *Sent:* Saturday, March 28, 2009 1:37 PM *To:* 'Discussion of IronPython' *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Dody Gunawinata *Sent:* Saturday, March 28, 2009 1:09 PM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We’re pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the ‘bytes’ and ‘bytearray’ types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it’s key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses “adaptive compilation” by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you’re only going to execute a method a few times, it’s typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the –O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There’s also a few minor changes since IronPython 2.0.1 that are worth calling out here: · IronPython.msi now installs NGEN’ed binaries
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
Any updated timeline on this (IronPython 2.6/ASP.Net Integration)? Just wanted to check in and see where it was on the list. Thanks, Adam 2009/3/30 Jimmy Schementi jimmy.scheme...@microsoft.com A IronPython 2.6 version of the ASP.NET integration will be out shortly, I have to get time to make a build and get it sent over to the ASP.NETteam. I’m working through some other things I need to get done first, but assume two weeks. *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Adam Brand *Sent:* Saturday, March 28, 2009 1:37 PM *To:* 'Discussion of IronPython' *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Dody Gunawinata *Sent:* Saturday, March 28, 2009 1:09 PM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We’re pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the ‘bytes’ and ‘bytearray’ types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it’s key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses “adaptive compilation” by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you’re only going to execute a method a few times, it’s typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the –O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There’s also a few minor changes since IronPython 2.0.1 that are worth calling out here: · IronPython.msi now installs NGEN’ed binaries by default · IronPython.msi now offers a little more selection with respect to what you’d like to install. For example, Silverlight templates are optional · The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically · The -X:PreferComInteropAssembly flag has been removed. All COM interop is now done through normal COM dispatch You can download IronPython 2.6 Alpha 1 at: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=22982 The IronPython Team ___ 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 -- nomadlife.org ___ Users mailing list Users@lists.ironpython.com http
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
Rather than just releasing builds, I'm waiting on the OK from the ASP.NET to release to source code for it, so it can be included in the IronPython releases and the Codeplex sources/daily builds. That seems like a much better solution. =) I'll keep you posted (I've been in conference-mode for the past couple months, so things have been slow, sorry!). From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Tuesday, May 05, 2009 5:39 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any updated timeline on this (IronPython 2.6/ASP.Net Integration)? Just wanted to check in and see where it was on the list. Thanks, Adam 2009/3/30 Jimmy Schementi jimmy.scheme...@microsoft.commailto:jimmy.scheme...@microsoft.com A IronPython 2.6 version of the ASP.NEThttp://ASP.NET integration will be out shortly, I have to get time to make a build and get it sent over to the ASP.NEThttp://ASP.NET team. I'm working through some other things I need to get done first, but assume two weeks. From: users-boun...@lists.ironpython.commailto:users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.commailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Saturday, March 28, 2009 1:37 PM To: 'Discussion of IronPython' Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.commailto:users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.commailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.commailto:giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the -O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There's also a few minor changes since IronPython 2.0.1 that are worth calling out here: * IronPython.msi now installs NGEN'ed binaries by default * IronPython.msi now offers a little more selection with respect to what you'd like to install. For example, Silverlight templates are optional * The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
That is great news, and a great solution! Thanks! Adam From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jimmy Schementi Sent: Tuesday, May 05, 2009 9:25 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Rather than just releasing builds, I'm waiting on the OK from the ASP.NET to release to source code for it, so it can be included in the IronPython releases and the Codeplex sources/daily builds. That seems like a much better solution. =) I'll keep you posted (I've been in conference-mode for the past couple months, so things have been slow, sorry!). From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Tuesday, May 05, 2009 5:39 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any updated timeline on this (IronPython 2.6/ASP.Net Integration)? Just wanted to check in and see where it was on the list. Thanks, Adam 2009/3/30 Jimmy Schementi jimmy.scheme...@microsoft.com A IronPython 2.6 version of the ASP.NET integration will be out shortly, I have to get time to make a build and get it sent over to the ASP.NET team. I'm working through some other things I need to get done first, but assume two weeks. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Saturday, March 28, 2009 1:37 PM To: 'Discussion of IronPython' Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the -O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There's also a few minor changes since IronPython 2.0.1 that are worth calling out here: . IronPython.msi now installs NGEN'ed binaries by default . IronPython.msi now offers a little more selection with respect to what you'd like to install. For example, Silverlight templates are optional . The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
I guess I really meant 3 weeks, because I was doing Lang.NET conference stuff all this past week. Sorry for the wait. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Thursday, April 16, 2009 11:12 AM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Is there any updated timeline on this? Looking forward to it :-). I'm sure you're swamped...if there is anything the community can do to speed this up please let us know. Thanks, Adam On Mon, Mar 30, 2009 at 4:44 PM, Jimmy Schementi jimmy.scheme...@microsoft.commailto:jimmy.scheme...@microsoft.com wrote: A IronPython 2.6 version of the ASP.NEThttp://ASP.NET integration will be out shortly, I have to get time to make a build and get it sent over to the ASP.NEThttp://ASP.NET team. I'm working through some other things I need to get done first, but assume two weeks. From: users-boun...@lists.ironpython.commailto:users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.commailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Saturday, March 28, 2009 1:37 PM To: 'Discussion of IronPython' Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.commailto:users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.commailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.commailto:giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the -O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There's also a few minor changes since IronPython 2.0.1 that are worth calling out here: * IronPython.msi now installs NGEN'ed binaries by default * IronPython.msi now offers a little more selection with respect to what you'd like to install. For example, Silverlight templates are optional * The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically * The -X:PreferComInteropAssembly flag has been removed. All COM interop is now done through normal COM dispatch You can download IronPython 2.6 Alpha
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
No worries.just excited to get it J. Thanks for continuing to work on it. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jimmy Schementi Sent: Friday, April 17, 2009 12:12 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 I guess I really meant 3 weeks, because I was doing Lang.NET conference stuff all this past week. Sorry for the wait. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Thursday, April 16, 2009 11:12 AM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Is there any updated timeline on this? Looking forward to it :-). I'm sure you're swamped...if there is anything the community can do to speed this up please let us know. Thanks, Adam On Mon, Mar 30, 2009 at 4:44 PM, Jimmy Schementi jimmy.scheme...@microsoft.com wrote: A IronPython 2.6 version of the ASP.NET integration will be out shortly, I have to get time to make a build and get it sent over to the ASP.NET team. I'm working through some other things I need to get done first, but assume two weeks. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Saturday, March 28, 2009 1:37 PM To: 'Discussion of IronPython' Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the -O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There's also a few minor changes since IronPython 2.0.1 that are worth calling out here: . IronPython.msi now installs NGEN'ed binaries by default . IronPython.msi now offers a little more selection with respect to what you'd like to install. For example, Silverlight templates are optional . The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically . The -X:PreferComInteropAssembly flag has been removed. All COM interop
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
Is there any updated timeline on this? Looking forward to it :-). I'm sure you're swamped...if there is anything the community can do to speed this up please let us know. Thanks, Adam On Mon, Mar 30, 2009 at 4:44 PM, Jimmy Schementi jimmy.scheme...@microsoft.com wrote: A IronPython 2.6 version of the ASP.NET integration will be out shortly, I have to get time to make a build and get it sent over to the ASP.NETteam. I’m working through some other things I need to get done first, but assume two weeks. *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Adam Brand *Sent:* Saturday, March 28, 2009 1:37 PM *To:* 'Discussion of IronPython' *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Dody Gunawinata *Sent:* Saturday, March 28, 2009 1:09 PM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We’re pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the ‘bytes’ and ‘bytearray’ types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it’s key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses “adaptive compilation” by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you’re only going to execute a method a few times, it’s typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the –O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There’s also a few minor changes since IronPython 2.0.1 that are worth calling out here: · IronPython.msi now installs NGEN’ed binaries by default · IronPython.msi now offers a little more selection with respect to what you’d like to install. For example, Silverlight templates are optional · The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically · The -X:PreferComInteropAssembly flag has been removed. All COM interop is now done through normal COM dispatch You can download IronPython 2.6 Alpha 1 at: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=22982 The IronPython Team ___ 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 -- nomadlife.org
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
I think Intellisense is critical for static language development - especially since we have to put up with compilation there. In dynamic language, we have REPL - now that's a productivity feature. Anyway, I wish the DynamicPageFilter module (the one powering IP ASP.Net) has the same source policy as IP or MVC for ASP.Net. This way we can patch the runtime ourselves to keep it up to date with the latest IronPython gizmos. One other way out for this is to use NWSGI.Net and build yet another web framework on top of Python that uses asp.net existing components;which should be fun but I rather build some cool applications than building a framework. Dody G. 2009/3/30 Leighton Haynes lhay...@gemcomsoftware.com I have to say – Intellisense is very high on our wishlist – we have many developers unfamiliar with Python, and Intellisense would ease the transition a lot. Cheers, Leighton Haynes Gemcom Software International *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *cur...@acm.org *Sent:* Monday, 30 March 2009 6:55 AM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Intellisense is a cosmetic feature at best. It's obviously nice to have, but it can't actually be *that* important to anyone...it's not like the information isn't available via other means. 2009/3/29 Howland-Rose, Kyle kyle.howland-r...@aar.com.au Hi Adam, About intellisense is not a major blocker for iron python adoption. Unfortunately I think it might be. The commercial world is all about productivity. I did a survey at work about replacing a well-known development environment with eclipse and the result was our only real requirement is intellisense. Cheers, Kyle -- *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Dody Gunawinata *Sent:* Monday, 30 March 2009 6:57 AM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 I think the fact that there are more users for Assembly for Web Pages and AJAX on ALGOL than IronPython for ASP.Net contributes to the delay in updates. It's too bad for us that got addicted to the elegance of the solution in the first place. I remember a couple of months ago about updated support for intellisense in IP for ASP.Net, etc. Those are nice to have but I think an updated IP would be enough to make everybody involved ecstatic. I got a feeling intellisense is not a major blocker for iron python adoption. 2009/3/28 Adam Brand ad...@silverkeytech.com Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Dody Gunawinata *Sent:* Saturday, March 28, 2009 1:09 PM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We’re pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the ‘bytes’ and ‘bytearray’ types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it’s key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses “adaptive compilation” by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you’re only going to execute a method a few times, it’s typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
A IronPython 2.6 version of the ASP.NET integration will be out shortly, I have to get time to make a build and get it sent over to the ASP.NET team. I'm working through some other things I need to get done first, but assume two weeks. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Saturday, March 28, 2009 1:37 PM To: 'Discussion of IronPython' Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.commailto:giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the -O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There's also a few minor changes since IronPython 2.0.1 that are worth calling out here: * IronPython.msi now installs NGEN'ed binaries by default * IronPython.msi now offers a little more selection with respect to what you'd like to install. For example, Silverlight templates are optional * The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically * The -X:PreferComInteropAssembly flag has been removed. All COM interop is now done through normal COM dispatch You can download IronPython 2.6 Alpha 1 at: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=22982 The IronPython Team ___ Users mailing list Users@lists.ironpython.commailto:Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com ___ Users mailing list Users@lists.ironpython.commailto:Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com -- nomadlife.orghttp://nomadlife.org ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
Fantastic! If you need any help in testing, let us know of course J. Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Jimmy Schementi Sent: Monday, March 30, 2009 4:45 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 A IronPython 2.6 version of the ASP.NET integration will be out shortly, I have to get time to make a build and get it sent over to the ASP.NET team. I'm working through some other things I need to get done first, but assume two weeks. From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Adam Brand Sent: Saturday, March 28, 2009 1:37 PM To: 'Discussion of IronPython' Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the -O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There's also a few minor changes since IronPython 2.0.1 that are worth calling out here: . IronPython.msi now installs NGEN'ed binaries by default . IronPython.msi now offers a little more selection with respect to what you'd like to install. For example, Silverlight templates are optional . The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically . The -X:PreferComInteropAssembly flag has been removed. All COM interop is now done through normal COM dispatch You can download IronPython 2.6 Alpha 1 at: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=22982 The IronPython Team ___ 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 -- nomadlife.org ___ Users mailing list
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
I think the fact that there are more users for Assembly for Web Pages and AJAX on ALGOL than IronPython for ASP.Net contributes to the delay in updates. It's too bad for us that got addicted to the elegance of the solution in the first place. I remember a couple of months ago about updated support for intellisense in IP for ASP.Net, etc. Those are nice to have but I think an updated IP would be enough to make everybody involved ecstatic. I got a feeling intellisense is not a major blocker for iron python adoption. 2009/3/28 Adam Brand ad...@silverkeytech.com Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Dody Gunawinata *Sent:* Saturday, March 28, 2009 1:09 PM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We’re pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the ‘bytes’ and ‘bytearray’ types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it’s key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses “adaptive compilation” by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you’re only going to execute a method a few times, it’s typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the –O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There’s also a few minor changes since IronPython 2.0.1 that are worth calling out here: · IronPython.msi now installs NGEN’ed binaries by default · IronPython.msi now offers a little more selection with respect to what you’d like to install. For example, Silverlight templates are optional · The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically · The -X:PreferComInteropAssembly flag has been removed. All COM interop is now done through normal COM dispatch You can download IronPython 2.6 Alpha 1 at: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=22982 The IronPython Team ___ 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 -- nomadlife.org ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com -- nomadlife.org ___ Users mailing list Users
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
Hi Adam, About intellisense is not a major blocker for iron python adoption. Unfortunately I think it might be. The commercial world is all about productivity. I did a survey at work about replacing a well-known development environment with eclipse and the result was our only real requirement is intellisense. Cheers, Kyle From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Monday, 30 March 2009 6:57 AM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 I think the fact that there are more users for Assembly for Web Pages and AJAX on ALGOL than IronPython for ASP.Net contributes to the delay in updates. It's too bad for us that got addicted to the elegance of the solution in the first place. I remember a couple of months ago about updated support for intellisense in IP for ASP.Net, etc. Those are nice to have but I think an updated IP would be enough to make everybody involved ecstatic. I got a feeling intellisense is not a major blocker for iron python adoption. 2009/3/28 Adam Brand ad...@silverkeytech.com Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the -O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There's also a few minor changes since IronPython 2.0.1 that are worth calling out here: * IronPython.msi now installs NGEN'ed binaries by default * IronPython.msi now offers a little more selection with respect to what you'd like to install. For example, Silverlight templates are optional * The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
Intellisense is a cosmetic feature at best. It's obviously nice to have, but it can't actually be *that* important to anyone...it's not like the information isn't available via other means. 2009/3/29 Howland-Rose, Kyle kyle.howland-r...@aar.com.au Hi Adam, About intellisense is not a major blocker for iron python adoption. Unfortunately I think it might be. The commercial world is all about productivity. I did a survey at work about replacing a well-known development environment with eclipse and the result was our only real requirement is intellisense. Cheers, Kyle -- *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Dody Gunawinata *Sent:* Monday, 30 March 2009 6:57 AM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 I think the fact that there are more users for Assembly for Web Pages and AJAX on ALGOL than IronPython for ASP.Net contributes to the delay in updates. It's too bad for us that got addicted to the elegance of the solution in the first place. I remember a couple of months ago about updated support for intellisense in IP for ASP.Net, etc. Those are nice to have but I think an updated IP would be enough to make everybody involved ecstatic. I got a feeling intellisense is not a major blocker for iron python adoption. 2009/3/28 Adam Brand ad...@silverkeytech.com Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies *From:* users-boun...@lists.ironpython.com [mailto: users-boun...@lists.ironpython.com] *On Behalf Of *Dody Gunawinata *Sent:* Saturday, March 28, 2009 1:09 PM *To:* Discussion of IronPython *Subject:* Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We’re pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the ‘bytes’ and ‘bytearray’ types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it’s key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses “adaptive compilation” by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you’re only going to execute a method a few times, it’s typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the –O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There’s also a few minor changes since IronPython 2.0.1 that are worth calling out here: · IronPython.msi now installs NGEN’ed binaries by default · IronPython.msi now offers a little more selection with respect to what you’d like to install. For example, Silverlight templates are optional · The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically · The -X:PreferComInteropAssembly flag has been
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
I suggest that intellisense is a productivity feature. I know that is how it is considered where I work. Is productivity cosmetic? Massively :) From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of cur...@acm.org Sent: Monday, 30 March 2009 9:55 AM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Intellisense is a cosmetic feature at best. It's obviously nice to have, but it can't actually be that important to anyone...it's not like the information isn't available via other means. 2009/3/29 Howland-Rose, Kyle kyle.howland-r...@aar.com.au Hi Adam, About intellisense is not a major blocker for iron python adoption. Unfortunately I think it might be. The commercial world is all about productivity. I did a survey at work about replacing a well-known development environment with eclipse and the result was our only real requirement is intellisense. Cheers, Kyle From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Monday, 30 March 2009 6:57 AM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 I think the fact that there are more users for Assembly for Web Pages and AJAX on ALGOL than IronPython for ASP.Net contributes to the delay in updates. It's too bad for us that got addicted to the elegance of the solution in the first place. I remember a couple of months ago about updated support for intellisense in IP for ASP.Net, etc. Those are nice to have but I think an updated IP would be enough to make everybody involved ecstatic. I got a feeling intellisense is not a major blocker for iron python adoption. 2009/3/28 Adam Brand ad...@silverkeytech.com Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
I think that was directed at Dody.but now that you mention it, I'm sure there would be more adopters if there was more momentum behind ipy for asp.net rather than just ipy with intellisense. I suspect more people are developing web apps than not. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Howland-Rose, Kyle Sent: Sunday, March 29, 2009 3:20 PM To: d...@nomadlife.org; Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 Hi Adam, About intellisense is not a major blocker for iron python adoption. Unfortunately I think it might be. The commercial world is all about productivity. I did a survey at work about replacing a well-known development environment with eclipse and the result was our only real requirement is intellisense. Cheers, Kyle _ From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Monday, 30 March 2009 6:57 AM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 I think the fact that there are more users for Assembly for Web Pages and AJAX on ALGOL than IronPython for ASP.Net contributes to the delay in updates. It's too bad for us that got addicted to the elegance of the solution in the first place. I remember a couple of months ago about updated support for intellisense in IP for ASP.Net, etc. Those are nice to have but I think an updated IP would be enough to make everybody involved ecstatic. I got a feeling intellisense is not a major blocker for iron python adoption. 2009/3/28 Adam Brand ad...@silverkeytech.com Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the -O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There's also a few minor changes since IronPython 2.0.1 that are worth calling out here: . IronPython.msi now installs NGEN'ed binaries by default . IronPython.msi now offers a little more selection with respect to what you'd like to install. For example, Silverlight templates are optional . The default installation location of IronPython.msi no longer indicates whether the 2.6
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We’re pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the ‘bytes’ and ‘bytearray’ types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it’s key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses “adaptive compilation” by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you’re only going to execute a method a few times, it’s typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the –O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There’s also a few minor changes since IronPython 2.0.1 that are worth calling out here: · IronPython.msi now installs NGEN’ed binaries by default · IronPython.msi now offers a little more selection with respect to what you’d like to install. For example, Silverlight templates are optional · The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically · The -X:PreferComInteropAssembly flag has been removed. All COM interop is now done through normal COM dispatch You can download IronPython 2.6 Alpha 1 at: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=22982 The IronPython Team ___ 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 -- nomadlife.org ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
Any update on the timeline for getting IronPython for ASP.Net updated? This would make a world of difference for our IronPython-based web app. Adam Adam Brand SilverKey Technologies From: users-boun...@lists.ironpython.com [mailto:users-boun...@lists.ironpython.com] On Behalf Of Dody Gunawinata Sent: Saturday, March 28, 2009 1:09 PM To: Discussion of IronPython Subject: Re: [IronPython] Announcing IronPython 2.6 Alpha 1 This is awesome. Web application can benefit from this adaptive compilation approach a lot - especially for low trafficked sites. On Thu, Mar 26, 2009 at 11:08 PM, Giles Thomas giles.tho...@resolversystems.com wrote: Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We're pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the 'bytes' and 'bytearray' types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it's key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses adaptive compilation by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you're only going to execute a method a few times, it's typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the -O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There's also a few minor changes since IronPython 2.0.1 that are worth calling out here: . IronPython.msi now installs NGEN'ed binaries by default . IronPython.msi now offers a little more selection with respect to what you'd like to install. For example, Silverlight templates are optional . The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically . The -X:PreferComInteropAssembly flag has been removed. All COM interop is now done through normal COM dispatch You can download IronPython 2.6 Alpha 1 at: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=22982 The IronPython Team ___ 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 -- nomadlife.org ___ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
Re: [IronPython] Announcing IronPython 2.6 Alpha 1
Dave, This is great news, congratulations to the IP team on this release! We'll do a test-port of Resolver One early next week and will reply to the list with any issues we find. Cheers, Giles Dave Fugate wrote: Hello Python Community, We’re pleased to announce the release of IronPython 2.6 Alpha 1. As you might imagine, this release is all about supporting new CPython 2.6 features such as the ‘bytes’ and ‘bytearray’ types (PEP 3112), decorators for classes (PEP 3129), advanced string formatting (PEP 3101), etc. The minimum .NET version required for this release is the same as IronPython 2.0; namely .NET 2.0 Service Pack 1. Unlike the 2.0 series of IronPython, we plan to release only a couple Alphas and Betas of IronPython 2.6. As such, it’s key that we get your feedback on the release(s) quickly to incorporate requested changes. Besides CPython 2.6 features, another significant change in this release is that ipy.exe now uses “adaptive compilation” by default. Adaptive compilation is a technique in which IronPython: 1. Interprets and executes Python method calls up to /N/ times for a given method. If you’re only going to execute a method a few times, it’s typically faster to interpret the method instead of compiling and executing it 2. Compiles and executes the Python method call on the /N+1/ invocation of the method. Compilation of a Python method is a heavyweight operation, but we can reuse the result for subsequent invocations 3. Reuses the previously compiled method for new calls to the Python method. This operation is much faster than interpreting the method call as the method was already compiled in the previous step The reason for this change is that it provides a nice performance gain for Python code containing lots of functions/methods that only get called a few times. All this said, this feature is still undergoing active development and as a consequence some Python scripts may actually run slower with it turned on. For this reason, our old default mode of running Python scripts is still available by passing the –O or -D flags to ipy.exe. Any feedback on how this new feature affects your IronPython applications performance-wise would be greatly appreciated. There’s also a few minor changes since IronPython 2.0.1 that are worth calling out here: · IronPython.msi now installs NGEN’ed binaries by default · IronPython.msi now offers a little more selection with respect to what you’d like to install. For example, Silverlight templates are optional · The default installation location of IronPython.msi no longer indicates whether the 2.6 release is an Alpha, Beta, or a patched release. Future IronPython 2.6 installations will replace previous 2.6 releases which will be uninstalled automatically · The -X:PreferComInteropAssembly flag has been removed. All COM interop is now done through normal COM dispatch You can download IronPython 2.6 Alpha 1 at: http://ironpython.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=22982 The IronPython Team ___ 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
