On Sat, Sep 26, 2009 at 2:34 PM, Markus Törnqvist <m...@nysv.org> wrote: > On Sat, Sep 26, 2009 at 09:55:43AM -0600, Jeff Hardy wrote: > > First off, there's so much randomality going on here it's impossible, > am I missing out on something everyone knows but me? > >  Could not load type 'Microsoft.Scripting.Runtime.CodeContext' from assembly >  'Microsoft.Scripting, Version=1.0.0.0, Culture=neutral, >  PublicKeyToken=31bf3856ad364e35'. > > ...
This is proably due to the assemblyBindings. I'll try to get a new build of NWSGI out ASAP. but I'm strapped for time. Sorry. > > Is the XML extremely sensitive to newlines and stuff? > > The ONLY pattern I've been able to discern is that: > 1. requests sometimes take a LONG time, especially the first time around This is to be expected. IronPython's straup times are less than stellar. > 2. if I reload in mid-request, I might get different effects This is odd. > >>What do you have SESSION_ENGINE set to? Also, have you read >>http://docs.djangoproject.com/en/dev/topics/http/sessions/? I have had >>this working in the past, so I don't think IronPython's import system >>is the cause here. > > The first time it was unset, so it defaulted to > django.contrib.sessions.backends.db > > Then I set it explicitly and it still failed. Try setting it to 'django.contrib.sessions.backends.cache' and setting CACHE_BACKEND = 'locmem:///'. I've used that combo in the past and it has worked for me. > Hope any of this helps..? Ttry going back to NWSGI 2.0 B2 and IronPython 2.6 B2 and see if that works any better. Bit by bit, things should come together. I have had large parts of django working, so I know it's possible. I really wish I had more time to look at this, but all I can do right now is offer advice :). - Jeff _______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
