[IronPython] Django, __unicode__, and #20366

[Vernon Cole]

Actually there is a project underway at the University of Toronto as we
speak to port Django to Python 3. See Porting Django to Python
3<http://groups.google.com/group/django-developers/browse_frm/thread/bf9d8808ee5aadb4/4ec8330ae28ce4e3?lnk=gst&q=python+3#4ec8330ae28ce4e3>on
the django developers group.
   I think it might be a Really Good idea if someone with an IronPython
interest were to volunteer to help the group.  Personally, I'm going to be
rather busy getting my django-capable version of adodbapi ready.) Perhaps
some of you might want to check them out. In my experience Python 3 support
and IronPython support go hand in hand.
--
Vernon Cole


On Sun, Jan 31, 2010 at 12:25 PM, Michael Foord
<fuzzyman at voidspace.org.uk>wrote:

> On 31/01/2010 01:21, Jeff Hardy wrote:
>
>> Hi all,
>> I've got a question regarding __unicode__ and issue #20366[0]. Django
>> explicitly encourages the use of __unicode__ on models[1], which would
>> not be available on IronPython. Also, they have some lazy evaluation
>> functions that depend on differences between str and unicode, and
>> default to using __unicode__. Now, these differences could be worked
>> around in Django, but I wonder if that's the right place for them.
>>
> There's *unlikely* to be an easy fix in IronPython any time soon, although
> I would love to be proved wrong. The Django team have *explicitly* said that
> they are open to patches (or even just bug reports) to make Django
> compatible with IronPython.
>
>
>  I
>> also have no idea how this will play out under 3.0.
>>
>>
>>
>
> Django is not expecting to move to Python 3 for quite some time as I
> understand it.
>
>
>  I'm working around by checking `str is unicode`; I'm not sure there's
>> really a better option.
>>
>>
>
> That sounds like a good solution to me.
>
>
>  - Jeff
>>
>>
>> [0] http://ironpython.codeplex.com/WorkItem/View.aspx?WorkItemId=20366
>>
>>
> I still think the partial-fix I suggest in that issue would be much better
> than the current situation...
>
> All the best,
>
> Michael
>
>
>  [1]
>> http://docs.djangoproject.com/en/1.1/ref/models/instances/#django.db.models.Model.__unicode__
>> _______________________________________________
>> Users mailing list
>> Users at lists.ironpython.com
>> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>>
>>
>
>
> --
> http://www.ironpythoninaction.com/
> http://www.voidspace.org.uk/blog
>
> READ CAREFULLY. By accepting and reading this email you agree, on behalf of
> your employer, to release me from all obligations and waivers arising from
> any and all NON-NEGOTIATED agreements, licenses, terms-of-service,
> shrinkwrap, clickwrap, browsewrap, confidentiality, non-disclosure,
> non-compete and acceptable use policies (”BOGUS AGREEMENTS”) that I have
> entered into with your employer, its partners, licensors, agents and
> assigns, in perpetuity, without prejudice to my ongoing rights and
> privileges. You further represent that you have the authority to release me
> from any BOGUS AGREEMENTS on behalf of your employer.
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20100201/658f45cd/attachment.html>