<!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 9:11 PM, Glyph Lefkowitz wrote:
<blockquote
cite="mid:5D5CC0A9-BD43-4496-872C-B70C5FC77490@twistedmatrix.com"
type="cite"><br>
<div>
<div>On Jan 20, 2011, at 12:02 AM, Glenn Linderman wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite"><span class="Apple-style-span"
style="border-collapse: separate; font-family: Menlo;
font-style: normal; font-variant: normal; font-weight:
normal; letter-spacing: normal; line-height: normal;
orphans: 2; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
font-size: medium;"><span class="Apple-style-span"
style="color: rgb(51, 0, 51);">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>
</span></span></blockquote>
</div>
<br>
<div>Is it really? You already had to type 'import', presumably
if you can think in Python you can think in ASCII.</div>
</blockquote>
<br>
There is a difference between memorizing and typing keywords, and
inventing new names in non-native scripts. It is hard to even
invent all the names in one's native language; if restricted to
inventing them, even some of them, in some non-native script such as
ASCII, it is just brain-burden indeed.<br>
<br>
<blockquote
cite="mid:5D5CC0A9-BD43-4496-872C-B70C5FC77490@twistedmatrix.com"
type="cite">
<div><br>
</div>
<div>(After my experiences with namespace crowding in Twisted, I'm
inclined to suggest something more like "import
m_07117FE4A1EBD544965DC19573183DA2 as café" - then I never need
to worry about "café2" looking ugly or "cafe" being incompatible
:).)</div>
<div><br>
</div>
</blockquote>
<br>
Now if the stuff after m_ was the hex UTF-8 of "café", that could
get interesting :) But now you are talking about automating the
creation of ASCII file names from the actual non-ASCII names of the
modules, or something. Sadly, the module is not required to contain
its name, so if it differs from the filename, some global view or
non-Python annotation would be required to create/maintain the
mapping. [This paragraph is only semi-serious, like yours.]<br>
<br>
<br>
</body>
</html>