On Thu, Mar 27, 2008 at 4:21 PM, Martin v. Löwis <[EMAIL PROTECTED]> wrote: > No hurt feelings, no. However, I would find it useful if you could > add specific reservations and doubts to that. What aspects of Django > (that I perhaps haven't touch yet) do you consider unmaintainable > under such approach?
The specific issues I've run into so far: * Exception-catching syntax (i.e. ``except Whatever as e`` vs. ``except Whatever, e``). * Unicode literals (u'...'). Those are the show-stoppers (for me -- maybe I'm just missing something?), but I'm actually more worried about the subtle differences between str/unicode and bytes/str... I suspect there'll be many subtle bugs there. Ditto anything using io, really, because the new io library isn't in any way the same as the old one (in a good way :) I'm also just worried about the uglyness of code needed to maintain something like this. Like about all the ImportErrors we'll have to catch once all the stdlib reorg happens... Jacob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
