-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yang Zhang wrote: > Actually, this is only because Python 3 str is Python 2 unicode. Python > 2 (which I'm currently using, and which I believe most of the world is > using) str is a physical string of bytes, not a logical/decoded > character string. Python 2.6 introduces bytes as a synonym for str, but > I am using Python 2.5 at the moment.
This is all pedantically true, but it is still a really bad way to structure your program? Did you read the Joel Unicode and character sets link? It was because Python 2 messed up on bytes versus strings versus unicode that they had to clean it up in Python 3. It is also why the SQLite wrappers in Python 2 return blobs as the buffer type so that there is no accidental mingling of bytes and strings. (Disclosure: I am the author of the APSW wrapper) SQLite *only* supports Unicode strings. Other databases do support non-Unicode strings, character set conversions and all that other complexity. It is your code and you can do whatever pleases you. However the advice still stands - keep your strings and bytes/blobs separate, and using the buffer type in Python 2 (and bytes in Python 3) is an excellent way of doing that. The wrappers already do this because it is good practise. Roger -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkoR10IACgkQmOOfHg372QQyjwCfXTwHMBsdAznHfDZ8CeaQIGNH T64Anj5qvy6MjjL/K08xi5CPY7pxueEi =Zet9 -----END PGP SIGNATURE----- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
