On Oct 22, 6:06 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > On Mon, 2007-10-22 at 06:02 -0700, koenb wrote: > ... > > On the other hand, Malcolm closed the ticket today as wontfix, stating > > it is a bug inmarkdown. > > Though that may be true, I do not understand why themarkdownfilter > > in SVN is converting text to bytestrings first if themarkdownmodule > > understands unicode (or maybe it didn't before ?). > > That's exactly it: it is only in the recent 1.6b release thatMarkdown > started understanding Unicode at all and there's no way that Django's > going to ask everybody to do a forced upgrade just because a third-party > package has done something that appears to be an error.
You think that Unicode support is an error or i'm missing something? This problem appeared because API changed in python-markdown and django should support both versions for some time (checking python- markdown version for ex.). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
