NWSGI Release Rss Feed

Created Release: NWSGI 2.0 Release Candidate 1 (Sep 28, 2009)

jdhardy — Mon, 28 Sep 2009 15:02:00 GMT

NWSGI 2.0 Release Candidate 1 is the same as NWSGI 2.0 Beta 2, but is built against IronPython 2.6 RC1..

Released: NWSGI 2.0 Release Candidate 1 (Sep 28, 2009)

Mon, 28 Sep 2009 15:02:00 GMT

NWSGI 2.0 Release Candidate 1 is the same as NWSGI 2.0 Beta 2, but is built against IronPython 2.6 RC1..

Updated Release: NWSGI 2.0 Beta 2 (Aug 15, 2009)

jdhardy — Sat, 15 Aug 2009 19:22:19 GMT

This beta release of NWSGI is linked against IronPython 2.6 Beta 2.

It also fixes the following workitems:

The installer will no longer add NWSGI to the GAC, as that doesn't have much value if IronPython is not in the GAC as well.

Released: NWSGI 2.0 Beta 2 (Aug 15, 2009)

Sat, 15 Aug 2009 19:22:18 GMT

This beta release of NWSGI is linked against IronPython 2.6 Beta 2.

It also fixes the following workitems:

The installer will no longer add NWSGI to the GAC, as that doesn't have much value if IronPython is not in the GAC as well.

Updated Release: NWSGI 2.0 Beta 2 (Aug 15, 2009)

jdhardy — Sat, 15 Aug 2009 19:19:00 GMT

This beta release of NWSGI is linked against IronPython 2.6 Beta 2.

It also fixes the following workitems:

Updated Release: NWSGI 2.0 Beta 1 (Jun 18, 2009)

jdhardy — Wed, 17 Jun 2009 23:30:32 GMT

This is the first preview release of NWSGI 2.0. This is a major update to NWSGI that makes it easier to install and use and dramatically improves the management story.

What’s New

Easier configuration. In v1.0 there were different ways to configure NWSGI depending on your configuration. Now there is only one way to do it. Some of the more ambiguous options have also been cleaned up, and new ones added to support IronPython 2.6.

Better management UI. IIS 7 includes a rich UI framework for developing management extensions, but doesn’t have much documentation on it. Some spelunking with reflector showed me better ways to do pretty much everything; not much of the v1.0 management code is left.

Performance improvements. NWSGI will now cache the WSGI callable instead of reloading it each time.

Other misc. fixes. I really need to get into the habit of adding a Codeplex issue for each bug so that I can keep track of what I’ve fixed.

Requirements

NWSGI 2.0 Beta 1 requires IronPython 2.6 Beta 1.

Released: NWSGI 2.0 Beta 1 (Jun 18, 2009)

Wed, 17 Jun 2009 23:30:32 GMT

This is the first preview release of NWSGI 2.0. This is a major update to NWSGI that makes it easier to install and use and dramatically improves the management story.

What’s New

Easier configuration. In v1.0 there were different ways to configure NWSGI depending on your configuration. Now there is only one way to do it. Some of the more ambiguous options have also been cleaned up, and new ones added to support IronPython 2.6.

Better management UI. IIS 7 includes a rich UI framework for developing management extensions, but doesn’t have much documentation on it. Some spelunking with reflector showed me better ways to do pretty much everything; not much of the v1.0 management code is left.

Performance improvements. NWSGI will now cache the WSGI callable instead of reloading it each time.

Other misc. fixes. I really need to get into the habit of adding a Codeplex issue for each bug so that I can keep track of what I’ve fixed.

Requirements

NWSGI 2.0 Beta 1 requires IronPython 2.6 Beta 1.

Updated Release: NWSGI 2.0 Beta 1

jdhardy — Wed, 17 Jun 2009 00:23:50 GMT

This is the first preview release of NWSGI 2.0. This is a major update to NWSGI that makes it easier to install and use and dramatically improves the management story.

What’s New

Easier configuration. In v1.0 there were different ways to configure NWSGI depending on your configuration. Now there is only one way to do it. Some of the more ambiguous options have also been cleaned up, and new ones added to support IronPython 2.6.

Better management UI. IIS 7 includes a rich UI framework for developing management extensions, but doesn’t have much documentation on it. Some spelunking with reflector showed me better ways to do pretty much everything; not much of the v1.0 management code is left.

Performance improvements. NWSGI will now cache the WSGI callable instead of reloading it each time.

Other misc. fixes. I really need to get into the habit of adding a Codeplex issue for each bug so that I can keep track of what I’ve fixed.

Requirements

NWSGI 2.0 Beta 1 requires IronPython 2.6 Beta 1.

Created Release: NWSGI 1.1 Preview 3 (Jun 07, 2009)

jdhardy — Sun, 07 Jun 2009 17:50:57 GMT

NWSGI 1.1 Preview 3 is a refresh of Preview 2 that fixes issues with configuration on 32-bit platforms. The release can only be used for xcopy deployments.

Released: NWSGI 1.1 Preview 3 (Jun 07, 2009)

Sun, 07 Jun 2009 17:50:57 GMT

NWSGI 1.1 Preview 3 is a refresh of Preview 2 that fixes issues with configuration on 32-bit platforms. The release can only be used for xcopy deployments.

Created Release: NWSGI 1.1 Preview 2 (May 24, 2009)

jdhardy — Sun, 24 May 2009 22:29:06 GMT

NWSGI 1.1 Preview 2 is exactly the same as Preview 1, except linked against IronPython 2.6 Beta 1.

Released: NWSGI 1.1 Preview 2 (May 24, 2009)

Sun, 24 May 2009 22:29:06 GMT

NWSGI 1.1 Preview 2 is exactly the same as Preview 1, except linked against IronPython 2.6 Beta 1.

Updated Release: NWSGI 1.1 Preview 1 (Mar 29, 2009)

jdhardy — Sun, 29 Mar 2009 19:05:05 GMT

NWSGI 1.1 Preview 1 requires IronPython 2.6 alpha 1. This release only contains the zip release as the management UI is being overhauled and is not yet complete.

The following features/changes have been added to NWSGI:

Add "callable" attribute to scriptMapping to specify the callable for that script.
Allow for "virtual" scripts by extending callables to allow for package.module:callable.

This can avoid creating a .wsgi file in many scenarios. This can be used with wildcard mappings by specifying wildcardModule=":callable".

Use the "debug" attribute on system.web/compilation instead of on wsgi.

The changes to callables aren't especially well documented at the moment, unfortunately.

Released: NWSGI 1.1 Preview 1 (Mar 29, 2009)

Sun, 29 Mar 2009 19:05:05 GMT

Add "callable" attribute to scriptMapping to specify the callable for that script.
Allow for "virtual" scripts by extending callables to allow for package.module:callable.

This can avoid creating a .wsgi file in many scenarios. This can be used with wildcard mappings by specifying wildcardModule=":callable".

Use the "debug" attribute on system.web/compilation instead of on wsgi.

The changes to callables aren't especially well documented at the moment, unfortunately.

Created Release: NWSGI 1.1 Preview 1 (Mar 29, 2009)

jdhardy — Sun, 29 Mar 2009 18:49:44 GMT

NWSGI 1.1 Preview 1 requires IronPython 2.6 alpha 1. This release only copntains the zip release as the managemnt UI is being overhauled and is not yet complete.

The following features/changes have been added to NWSGI:

Add "callable" attribute to scriptMapping to specify the callable for that script.
Allow for "virtual" scripts by extending callables to allow for package.module:callable.

This can avoid creating a .wsgi file in many scenarios. This can be used with wildcard mappings by specifying wildcardModule=":callable".

Use the "debug" attribute on system.web/compilation instead of on wsgi.

The changes to callables aren't especially well documented at the moment, unfortunately.

Released: NWSGI 1.1 Preview 1 (Mar 29, 2009)

Sun, 29 Mar 2009 18:49:44 GMT

Add "callable" attribute to scriptMapping to specify the callable for that script.
Allow for "virtual" scripts by extending callables to allow for package.module:callable.

This can avoid creating a .wsgi file in many scenarios. This can be used with wildcard mappings by specifying wildcardModule=":callable".

Use the "debug" attribute on system.web/compilation instead of on wsgi.

The changes to callables aren't especially well documented at the moment, unfortunately.

Updated Release: NWSGI 1.0 (Dec 27, 2008)

jdhardy — Sun, 28 Dec 2008 00:35:39 GMT

NWSGI is an implementation of the WSGI Specification (PEP 333) for IronPython. It is implemented as an ASP.NET HttpHandler and is supported on IIS 6 and IIS 7 (and should work on any other ASP.NET-capable web server). NWSGI allows the integration of Python applications with existing ASP.NET facilities such as caching, sessions, and user management.

This release does not mean that any Python application will work. The underlying IronPython 2.0 engine is not yet complete. It is a nearly-complete implementation of the NWSGI specification, and any app that takes IronPython's limitations into account should work just fine.

NWSGI fully supports xcopy deployment and medium trust environments (with the caveat that parts of the Python standard library are not supported). There is also an installer available that provides a managment UI for IIS 7.

NWSGI requires IIS (6 or 7), IronPython 2.0, and .NET Framework 2.0 SP1. All downloads include the NWSGI assembly, basic documentation, and a HelloWorld sample. The installers also include the IIS management UI.

Released: NWSGI 1.0 (Dec 27, 2008)

Sun, 28 Dec 2008 00:35:39 GMT

Created Release: NWSGI 0.7 (Dec 04, 2008)

jdhardy — Fri, 05 Dec 2008 01:36:50 GMT

NWSGI is an ASP.NET HttpHandler that implements the PYthon WSGI specification (PEP 333). This release adds the following new features:

Session support
Proper Unicode handling
Wildcard mapping support
WSGI extensions are disabled by default.

The installers contain IIS7 managment UI components; the zip file does not. Only the zip file contains the Hello World example.

Released: NWSGI 0.7 (Dec 04, 2008)

Fri, 05 Dec 2008 01:36:48 GMT

NWSGI is an ASP.NET HttpHandler that implements the PYthon WSGI specification (PEP 333). This release adds the following new features:

Session support
Proper Unicode handling
Wildcard mapping support
WSGI extensions are disabled by default.

The installers contain IIS7 managment UI components; the zip file does not. Only the zip file contains the Hello World example.