When will Python 3 be fully deployed
nobody at nowhere.com
Wed Dec 9 20:25:40 CET 2009
On Wed, 09 Dec 2009 10:28:40 -0800, Rami Chowdhury wrote:
>> But on Unix, it's a square-peg-round-hole situation.
> I dunno, I find it rather useful not to have to faff about with
> encoding to/from when working with non-ASCII files (with non-ASCII
> filenames) on Linux.
For the kind of task I'm referring to, there is no encoding or decoding.
You get byte strings from argv, environ, files, etc, and pass them to
library functions. What those bytes "mean" as text (if anything) never
enters the equation.
For cases where you *need* text (e.g. GUIs), Python 3 makes the simplest
cases easier. The more complex cases (e.g. where each data source may have
its own encoding, or even multiple encodings) aren't much different
between Python 2 and Python 3.
More information about the Python-list