Jason Tackaberry wrote: > On Fri, 2006-12-01 at 16:50 +0100, Dirk Meyer wrote: >> Unicode in Python sucks! > > I wouldn't say it sucks. It has some warts, but overall I think it's > not bad. Why do you think it sucks? > > >>> First, when a string is a Unicode string does this mean that every >>> character is 2 or 4 bytes wide? >> No idea. > > Actually, Duncan, are you referring to the internal storage of that > string inside Python for unicode objects? If so, I also don't know. In > my last email I assumed you meant once the string is encoded as a > specific encoding type -- in that case each character is not necessarily >> 1 bytes.
Does really matter how the are stored internally. >> errors in any kind, kaa.beacon uses strings for filenames all the >> time, everything else is unicode. I suggest you do the same. > > A filename can be any arbitrary sequence of non-null bytes, with no > requirement that they decode using a specific encoding type, so it > actually makes good sense that filenames be str and never unicode. But > yes, beacon is where we came to this realization. :) What a simple rule, file names as is Thanks Guys. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freevo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-devel
