Eric Firing wrote:
> While you are at it, perhaps you can figure out how to stop 
> unicode_demo from generating an error:
>
>         driving unicode_demo.py
>   File "_tmp_unicode_demo.py", line 10
> SyntaxError: Non-ASCII character '\xe9' in file _tmp_unicode_demo.py 
> on line 10, but no encoding declared; see 
> http://www.python.org/peps/pep-0263.html for details
I have a fix for this I'll commit momentarily.  The backend_driver 
inserts non-comment lines before the -*- coding line.

As for Unicode literals in Python source, there is a third option, other 
than u'\xd7' or '×'.  Python will let you do u"\N{MULTIPLICATION SIGN}", 
which means you don't have to remember what \xd7 is.  For single 
characters like this, I don't see much advantage (you can just name the 
variable something obvious), but for longer strings with embedded 
unicode characters (like docstrings), this might be something to consider.

Cheers,
Mike

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Reply via email to