Hans-Christian Holm wrote: > My first reaction to Django was "hey, this looks nice, maybe it could be > ported to Boo, my favourite language at the moment?" On second thought, I'd > rather see Django run on IronPython. You could use Boo with that, if you > wanted to. I would be very interesting to see if Django+IronPython could run > in ASP.NET through some DjangoHttpHandler. I don't see why it shouldn't > (theoretically), unless there are some troublesome dependencies on libraries > would have to be ported to .NET first.
I am interested in that too. Unfortunately it is not possible to run Django with IronPython as it is --- IronPython doesn't support the Python standard library (pure Python modules are supported). During PyCon 2006 I had a brief conversation with Jim Hugunin about that. Let's hope they will find a way to support the rest (C modules). Otherwise we are talking about porting Django with all obvious downsides of this solution. Another problem is unresolved issues with MS SQL, which doesn't support limit-offset queries directly. While it is possible to use other databases from .Net environment, MS SQL native provider has the best performance. :-) Thanks, Eugene --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---