On Fri, Sep 25, 2009 at 12:22 PM, Markus Törnqvist <m...@nysv.org> wrote:
> I configured for 1.0.0.0 as Properties of Microsoft.Scripting.DLL says and
> 2.6.10920.0 for IronPython.dll.
>
> AND IT WORKS! :)

Good to know! (I haven't had time to respin NWSGI for RC1 yet -
hopefully this weekend). Once IronPython 2.6 final and NWSGI 2.0 are
released, all this version craziness should go away (for now).

>
> (My only outstanding issue is now
>
>  Line 9:          engine = __import__(settings.SESSION_ENGINE, {}, {}, [''])
>  Line 10:         session_key =
>  request.COOKIES.get(settings.SESSION_COOKIE_NAME, None)
>  Line 11:         request.session = engine.SessionStore(session_key)
>  Line 12:
>  Line 13:     def process_response(self, request, response):
>
> which is a Django error I'll have to fight with, hopefully it's not too bad :)

Wht's the error, exactly? I've probably seen it before.

> Here are the configuration tags if they'd help anyone else.
>
>    <!-- ATTEMPT AT FIXING NWSGI LINKED AGAINST 2.6B2 -->
>    <runtime>
>        <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
>            <dependentAssembly>
>                <assemblyIdentity name="IronPython" 
> publicKeyToken="31bf3856ad364e35" culture="neutral" />
>                <bindingRedirect oldVersion="2.6.0.20" 
> newVersion="2.6.10920.0" />
>            </dependentAssembly>
>            <dependentAssembly>
>                <assemblyIdentity name="Microsoft.Scripting" 
> publicKeyToken="31bf3856ad364e35" culture="neutral" />
>                <bindingRedirect oldVersion="0.9.6.20" newVersion="1.0.0.0" />
>            </dependentAssembly>
>        </assemblyBinding>
>    </runtime>

I hope you don't mind:
http://jdhardy.blogspot.com/2009/09/using-nwsgi-20-beta-2-with-ironpython.html.

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

Reply via email to