Sandro, it's obviously a good thing to do when using non-ASCII characters *in your code*. The problem is that this exception on my system showed up whenever the mimetypes.guess_type method was called, even if it is the only line of cod in source file (except the import line) and there are no non-ASCII characters in it. P.S. As I've said before this problem turned out to belong to Python's library itself and has nothing to do with Django.
On Oct 21, 3:59 pm, Sandro Dutra <hexo...@gmail.com> wrote: > To use unicode characters, I put on the top of source file: -*- coding: > utf-8 -*- and before any string I put an "u", like: u"My unicode string". On > templates, I save the file as utf-8. > > There's no workaround, only code. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
