<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#330033" bgcolor="#ffffff">
On 1/19/2011 8:39 PM, Toshio Kuratomi wrote:
<blockquote cite="mid:20110120043901.GR22400@unaka.lan" type="cite">use
this::<br>
<pre wrap=""> import cafe as café
When you do things this way you do not have to translate between unknown
encodings into unicode. Everything is within python source where you have
a defined encoding.
</pre>
</blockquote>
<br>
This is a great way of converting non-portable module names, if the
module ever leaves the bounds of its computer, and runs into
problems there.<br>
<br>
It may be that the best practices for writing platform portable
modules should include<br>
* ASCII module filenames<br>
* Code that can handle 16 or 32 bit Unicode<br>
* and likely some other things.<br>
<br>
But for local code, having to think up an ASCII name for a module
rather than use the obvious native-language name, is just
brain-burden when creating the code.<br>
<br>
Your demonstration of such an easy solution to the concerns you
raise convinces me more than ever that it is acceptable to allow
non-ASCII module names. For those programmers in a single locale
environment, it'll just work. And for those not in a single locale
environment, there is your above simple solution to achieve
portability without changing large numbers of lines of code.<br>
<br>
Glenn<br>
</body>
</html>