Re: PyISAPIe + 0.91: some backporting help required...

2006-08-17 Thread Scott Finnie
Thanks Jeremy. Time to look for plan B... Jeremy Dunck wrote: > On 8/17/06, Scott Finnie <[EMAIL PROTECTED]> wrote: >> from django.utils import httpwrappers as http >> #from ??? import signals >> #from ??? import dispatcher > > > The magic removal branch started at r1587; dispat

Re: PyISAPIe + 0.91: some backporting help required...

2006-08-17 Thread Jeremy Dunck
On 8/17/06, Scott Finnie <[EMAIL PROTECTED]> wrote: > from django.utils import httpwrappers as http > #from ??? import signals > #from ??? import dispatcher The magic removal branch started at r1587; dispatcher was introduced in r1714 on the branch, and the branch was merged on r2

Re: PyISAPIe + 0.91: some backporting help required...

2006-08-17 Thread Scott Finnie
Two reasons, one (I think) decent: 1. App is currently written to 0.91 and I want to get some feedback (that's the indecent answer) 2. My model makes extensive use of subtyping which isn't supported in 0.95 (hopefully the decent one...) Jeremy Dunck wrote: > On 8/17/06, Scott Finnie <[EMAIL PR

Re: PyISAPIe + 0.91: some backporting help required...

2006-08-17 Thread Jeremy Dunck
On 8/17/06, Scott Finnie <[EMAIL PROTECTED]> wrote: > However, the interface module (pyisapie.py) is written to post-MR > refactored APIs; would be grateful for a pointer on where they were > located in 0.91. Here's the obligatory question: Do you have a really good reason for being on 0.91? Bec

PyISAPIe + 0.91: some backporting help required...

2006-08-17 Thread Scott Finnie
Hello all, Trying to get above sorted to run django with IIS (per http://code.djangoproject.com/wiki/DjangoOnWindowsWithIISAndSQLServer). However, the interface module (pyisapie.py) is written to post-MR refactored APIs; would be grateful for a pointer on where they were located in 0.91. Her