Oh, and regarding your blog which insists I sign in to post :) You can set MultipleActiveResultSets=True in the connection string to get around the cursor problem. That's what I did w/ my provider when I was working on Django compat over at http://blogs.msdn.com/dinoviehland/archive/2008/03/17/ironpython-ms-sql-and-pep-249.aspx
I'm not sure if there's some horrible performance implications from that but it at least is a short term work around. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Hardy Sent: Tuesday, August 05, 2008 7:53 PM To: Discussion of IronPython Subject: [IronPython] NWSGI 0.4 released To coincide with the release of IronPython 2.0b4, NWSGI (http://codeplex.com/NWSGI) has been updated to version 0.4. This version also brings improvements to configuration and performance. IronPython itself has improved dramatically (kudos to the team for a fantastic job) and is now capable of running parts of Django, although some workarounds are still required. I can make it through the tutorial, and once I get some testing with 2.0b4 done I'll post patches as well. I'm going to start testing against some other applications as well, and post the results on my blog - jdhardy.blogspot.com - as well as the compatibilty pages on ironpython.info. -Jeff _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ Users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
