Hi, this has nothing to do with Django at all, it's a python thing. The encoding declaration needs to go on top of EVERY source code file if you the source code contains non-ASCII encoding. This has NOTHING to do with Django encoding or the encoding your database uses!
Now, slowly: When you exchanged MySQL with postgresql, there should have been no need to change much in your sources. Why are there suddenly non-ASCII characters in your sources? Or are you just trying out something? Kind regards Michael -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
