[Ironpython-users] Mono and Ironpython

[Pratik Paranjape]

Thanks for the inputs Vernon, Jeff.

Just checked Jeff's old posts and bitbucket page, it does not look pretty,
at least with my
current time constraints.

The only thing that I absolutely can not avoid using is the .NET library ,
so I can get away with
using cherrypy/ironpython as middle tier between clients and my existing
Django application. Its a low load
application.

If nothing works, eventually I can try mono-fastcgi, and write this part in
C#, but thats last resort, everything
else is in python.

Getting ironpython-django working will be cool though. I will try it out
outside the scope of current project.



On Wed, Apr 25, 2012 at 9:15 PM, Jeff Hardy <jdhardy at gmail.com> wrote:

> On Wed, Apr 25, 2012 at 8:34 AM, Vernon Cole <vernondcole at gmail.com>
> wrote:
> > Ummm... reality check...
> >
> > Patrik:
> >   I have been lurking on the django developers list (along with
> IronPython)
> > for several years hoping for exactly the combination you are
> suggesting.  I
> > am unaware that anyone has tackled the project of making django run on
> > IronPython yet, on either Windows or mono.  As I see it, there may be two
> > problems.
> > 1)  django has issues with strings being assumed to be 8-bit bytes.  This
> > has to be fixed to port django to Python 3, and I suggested that
> IronPython
> > would be a useful stepping stone in that effort, but no one took the bait
> > AFAIK.
> > 2)  django's built-in object relational mapper is targeted at four
> > databases: MySQL, PostgreSQL, SQLite, and Oracle.
> >  (see https://docs.djangoproject.com/en/dev/ref/databases/)
> > Of these four, I think that only SQLite is well supported by IronPython.
> > Oracle, MySQL and PostgresSQL are accessible from IronPython using my
> > adodbapi package, but it only works on Windows, since it relies on
> Microsoft
> > COM to reach the ODBC database engine (via traditional ADO).  My own
> efforts
> > to use pure ADO.NET database calls had a rather dismal result, and I
> > abandoned the branch.  To my knowledge, the only other PEP 249 database
> APIs
> > for IronPython are the group on fePy, which have not been maintained in
> > several years.  I am also unsure about the level of database support in
> > mono.
> >
> > If someone is working on support for django on IronPython, I would love
> to
> > be part of the project.
>
> I did work on it a bit a few years ago, and there's some out-of-date
> patches at https://bitbucket.org/jdhardy/django-ipy-patches.
>
> This was before IronPython was taking contributions, so getting fixes
> into IP was much harder. If anybody is interested in it, and is aware
> that there's a massive amount of work involved, you'd have my full
> support, and any fixes would be greatly appreciated.
>
> - Jeff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20120425/160e1c09/attachment.html>