On Mon, Aug 31, 2009 at 4:41 PM, Edward K. Ream<[email protected]> wrote:
> This may cause compatibility problems. The present laissez-faire > approach allows users to specify the encoding. Perhaps this is a bad > idea, but forcing utf-8 might cause confusion. I'd prefer to leave For run-script, it doesn't make sense to specify encoding since the files are only stored once and run immediately, in an encoding that's always supported by the python interpreter. > things as they are unless there is an urgent reason to change. To I think not being able to add unicode characters to scripts can be urgent (for some people, not me really - I rarely use non-ascii characters). The bonus is that it should be very easy to implement. Does running a script print 'ä' Work ok for you? If it does try defaultencoding 'ascii' (which is the default). > repeat, we can revisit this topic for Python 3k, which will happen > this year, if all goes well. We don't really need to consider py3k here, the same requirement applies for py3k (non-ascii python source files need to specify encoding if it has unicode literals). -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
