On Tue, 2007-04-17 at 16:11 +0000, [EMAIL PROTECTED] wrote: > Hi, > > As I use characters with accents, I got the following issue yesterday > when validating my models : > > mvmo.cv: Non-ASCII character '\xc3' in file /home/django/mvmo/../mvmo/ > cv/models. > py on line 111, but no encoding declared; see > http://www.python.org/peps/pep-026 > 3.html for details (models.py, line 111) > > Ok, so with this helpful error message, I could easily find that I had > to add > > # -*- coding: utf8 -*- > > at the beginning of my file to solve the issue. > > So my question is : why is not such a line added by default in > models.py so that such an issue never happens ?
The default encoding may not be utf-8. > You could have something like for a default models.py : > > # -*- coding: <set your encoding here> -*- > from django.db import models > > # Create your models here. > > Does it make sense ? Is it worth a ticket ? I don't think so. It's a line-ball call, though, for sure. See below for my reasoning. > would it be solved by the > unicode branch ? Not really -- although in that case there would be slightly more value in adding the encoding line, since bytestrings that aren't UTF-8 encoded will break in interesting ways. My main reason for not adding this: if you forget to add the encoding line, Python gives you a very clear error message and explains what you need to do to fix it. Sometimes that alerts you to the fact that you've accidently included non-ASCII characters (e.g. via cut-and-paste) and need to actually check the encoding -- such as when you've pasted from a document in Windows. If we automatically include such a line and it's wrong for some reason (because you're in Japan and prefer to use shift-JIS, or you're cursed to use Windows, so CP-1152 is a way of life), things will sort of work and you'll get an unexpected decoding error way down the track. As a programmer who makes mistakes, I like the early warning system a bit better. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
