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