[docs] [issue11230] "Full unicode import system" not in 3.2
report at bugs.python.org
Fri Feb 18 05:45:49 CET 2011
John <jh45dev at gmail.com> added the comment:
Victor asked "Which web page should updated/fixed?"
Answer: The Python 3.2 download page.
But what should it say?
The main point is that people like me, who remember seeing a statement about this a few months ago, may expect unicode to work in every conceivable situation, and a prominent warning that it's not *all* fixed yet, with a link to details in the documentation, would save them from trying things that don't work.
By the way, I hadn't grasped a simple point from issue 3080: I tested on *English* Windows by putting a Greek character in the path to some python modules. But the usual situation is where a *Greek* version of Windows has some Greek characters in the path, and from what you just wrote, that's OK now.
Python tracker <report at bugs.python.org>
More information about the docs