Comments on: Python, the text editor, and encoding http://www.softimageblog.com/archives/111#utm_source=rss&utm_medium=rss&utm_campaign=python-the-text-editor-and-encoding People and thoughts behind Softimage in production... Fri, 23 Jul 2010 12:23:34 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: diego nunes http://www.softimageblog.com/archives/111/comment-page-1#comment-17349 diego nunes Wed, 22 Oct 2008 16:10:11 +0000 http://www.xsi-blog.com/?p=111#comment-17349 . . Don't blame poor SciTE. It's my editor of choice since ever. The problem is that you're using non-ascii string in a Python source code without saying that to the compiler. PEP 263 (http://www.python.org/dev/peps/pep-0263) says you have a lot of options to do that (I, personally, like to use the second suggestes option). . . As Python is really cool to newbies, if you save your file as UTF-8 with BOM, Python will automatically understand that he's dealing with UTF-8 encoding and treat the strings properly. If you change the encoding in SciTE to "UTF-8 with BOM" or simply declare you encoding explicitly, you won't have any problems. . . Don’t blame poor SciTE. It’s my editor of choice since ever. The problem is that you’re using non-ascii string in a Python source code without saying that to the compiler. PEP 263 (http://www.python.org/dev/peps/pep-0263) says you have a lot of options to do that (I, personally, like to use the second suggestes option).
. . As Python is really cool to newbies, if you save your file as UTF-8 with BOM, Python will automatically understand that he’s dealing with UTF-8 encoding and treat the strings properly. If you change the encoding in SciTE to “UTF-8 with BOM” or simply declare you encoding explicitly, you won’t have any problems.

]]> By: ekeko http://www.softimageblog.com/archives/111/comment-page-1#comment-15340 ekeko Wed, 23 May 2007 11:21:44 +0000 http://www.xsi-blog.com/?p=111#comment-15340 Hi: going straight to the problem and not losing myself in nonsense comments: did you try with (encoding example): # -*- coding: iso-8859-1 -*- at the very first line of the file? check your |python-dir]\Lib\encodings\string_escape.py for a running example Hi:
going straight to the problem and not losing myself in nonsense comments:

did you try with (encoding example):

# -*- coding: iso-8859-1 -*-

at the very first line of the file?
check your |python-dir]\Lib\encodings\string_escape.py for a running example

]]> By: Luc-Eric http://www.softimageblog.com/archives/111/comment-page-1#comment-5741 Luc-Eric Wed, 30 Aug 2006 19:26:47 +0000 http://www.xsi-blog.com/?p=111#comment-5741 It because the file was saved as a unicode text file. the first bytes of a unicode text file are : 0xFF 0xFE, this is how editors like notepad know that the file isn''t ASCII It because the file was saved as a unicode text file.
the first bytes of a unicode text file are : 0xFF 0xFE,
this is how editors like notepad know that the file isn”t ASCII

]]> By: Daniele Niero http://www.softimageblog.com/archives/111/comment-page-1#comment-5724 Daniele Niero Tue, 29 Aug 2006 14:59:51 +0000 http://www.xsi-blog.com/?p=111#comment-5724 Yes! I have missed the real problem :) It doesn''t have to do with what I said :) Sorry Bernard. But now I''m very curios about that, and I tried to replicate the problem without any luck (apparently I still missing what exactly is). Can you post a simple code that generate this kind of error? Cheers, Daniele Yes! I have missed the real problem :) It doesn”t have to do with what I said :)
Sorry Bernard.
But now I”m very curios about that, and I tried to replicate the problem without any luck (apparently I still missing what exactly is). Can you post a simple code that generate this kind of error?

Cheers,
Daniele

]]> By: Daniele Niero http://www.softimageblog.com/archives/111/comment-page-1#comment-5723 Daniele Niero Tue, 29 Aug 2006 14:29:27 +0000 http://www.xsi-blog.com/?p=111#comment-5723 Maybe I missed the real problem, but it looks like an indentation problem. Different encoding = different way to indent the words... or am I wrong? since the indentation is part of the syntax, python is particularly expose to this kind of problem. This was my point... :) Maybe I missed the real problem, but it looks like an indentation problem. Different encoding = different way to indent the words… or am I wrong? since the indentation is part of the syntax, python is particularly expose to this kind of problem. This was my point… :)

]]> By: Bernard Lebel http://www.softimageblog.com/archives/111/comment-page-1#comment-5720 Bernard Lebel Tue, 29 Aug 2006 11:36:34 +0000 http://www.xsi-blog.com/?p=111#comment-5720 I don''t see what the syntax has to do with the encoding or the problem I have reported. But thanks for the suggestions. Bernard I don”t see what the syntax has to do with the encoding or the problem I have reported. But thanks for the suggestions.

Bernard

]]> By: Daniele Niero http://www.softimageblog.com/archives/111/comment-page-1#comment-5715 Daniele Niero Tue, 29 Aug 2006 09:27:35 +0000 http://www.xsi-blog.com/?p=111#comment-5715 Yes, this is a common problem with python. Personally I consider python a tool with very nice features, but with an horrible syntax. The "indent part of the syntax" approach instead using the most common brackets expose our code to this type of stupid syntax error. So is necessary using a good ide when coding in python. I suggest Komodo (commercial) or Eclipse with PyDev extensions. Yes, this is a common problem with python. Personally I consider python a tool with very nice features, but with an horrible syntax. The “indent part of the syntax” approach instead using the most common brackets expose our code to this type of stupid syntax error. So is necessary using a good ide when coding in python. I suggest Komodo (commercial) or Eclipse with PyDev extensions.

]]>