On Sat, 2008-04-12 at 03:24 -0700, fizban wrote: > I've fixed my issue by replacing smart_str with force_unicode in > django.contrib.markup (the portion about markdown obviously). > > Why is django (latest svn trunk) passing bytestring to markdown, which > is supposed to be fed by ascii or unicode? :\ > > Should I fill a ticket or is there a valid reason to do so? I mean, as > far as i can see it's just plain wrong..
It sounds like you're using markdown 1.7. Markdown recently made a massively backwards incompatible change: they used to accept only bytestrings, then they accepted bytestrings (UTF-8, ASCII, UTF-16, and some others) and now they only take unicode. We haven't yet incorporated the patch necessary to handle markdown 1.7 along with the earlier versions. That will go in soon, though -- there's already a ticket in Trac for it. Regards, Malcolm -- I don't have a solution, but I admire your problem. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
