PyISAPIe + django 1.2

[Mark L.]

Hello,

I've tried to make django 1.2 (current stable) work with IIS 7 (under
windows 7 x86_64) using PyISAPIe 1.1.0-rc4 and it appears, that the
django handler (PyISAPIe/Python/Examples/Django/pyisapie.py) is
outdated and very much so. For example, the signal dispatching code it
has is using the signatures from django 0.96, if I am reading it
right. There are other incompatibilities too, like the HttpRequest
subclass not providing the path_info attribute.

What is the current status of the module? Is it supported at all? If
not, maybe I should try to make it work? I've fixed the most trivial
things (like the ones outlined above) to see if I can make my apps run
under IIS at all, but I am sure, that there are more subtleties, since
django's core changed drastically between 0.96 and 1.2.

Meanwhile, if anyone has any compassion at all for this problem, you
are very welcome to suggest a temporary workaround (or a solid
solution!) at http://stackoverflow.com/questions/3651648/django-iis.

Thanks in advance,

Mark

[Phillip]

The module isn't supported at all and the Django folks didn't get
around to including it in the core, so it shouldn't be considered when
trying to get PyISAPIe+Django working.

If you look in the Examples folder, you'll see some info on how to get
it all set up with WSGI only, which is a better long-term solution.

Cheers,

Phillip

> solution!) athttp://stackoverflow.com/questions/3651648/django-iis.
>
> Thanks in advance,
>
> Mark

[Mark L.]

Hello,

Thanks a lot for the clarification here and on SO.

Indeed, using the generic wsgi handler, I've made it work in about ten
minutes, that's after struggling with the django-specific handler for
almost a whole day (made it work, though). Doh!

Is it worth the time to work on the django handler? What benefits does
it have compared to the generic wsgi one? I could probably take a stab
at it if it makes sense to do so.

Thanks again,

Mark