[Ironpython-users] Mono and Ironpython

[Vernon Cole]

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.
--
Vernon

 >>
>> >> On Apr 25, 2012 4:56 AM, "Pratik Paranjape" <pratikparanjape at gmail.com
>> >
>> >> wrote:
>> >>>
>> [...snip...]
>>
> . My aim is to use a
>> >>> .NET library with Django as
>> >>> front end. The library works fine with mono, was hoping to use ipy to
>> >>> call it in Django views.
>> >>>
>> >>> Thanks again.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20120425/6e4b58bf/attachment.html>