(original) (raw)
Of cource, I know, using Python3 is the best way.
But, there are libraries only supporting Python2 (i.e python-xlib).
Using Python2's dual-text system is not so difficult for me.
Because I'm Japanese, I had to handle Japanese with many charsets in every programs I made.
And I have one simple rule.
"Use unicode type all time.
Input must be converted to unicode soon.
Output must be converted to str late."
And, fixing this bug can open a can of worms ?
I think, we should open it.
IDLE needs cleanup such as removing too old codes.
2013/4/22 Terry Jan Reedy <tjreedy@udel.edu>
On 4/21/2013 4:20 PM, Andrew Svetlov wrote:To be clearer, it was closed a March 8. David reopened, but like Andrew, I am wary. One reason we made unicode the text type in Python 3 was that patching the Python 2 dual-text system became a bit like playing Whack-A-Mole
I think fixing this bug for python 2 can open a can of worms. Python 3
works correctly IIRC.
On Sun, Apr 21, 2013 at 7:47 PM, Tomoki Imai <tomo832@gmail.com> wrote:
Hi.
I found bug (I think) in IDLE.
That is, unicode literal in IDLE.
You can reconfirm it by executing following code in IDLE.
u'\\xe3\\x81\\x93\\xe3\\x82\\x93\\xe3\\x81\\xab\\xe3\\x81\\xa1\\xe3\\x81\\xaf'u"$B$3$s$K$A$O(B"
("$B$3$s$K$A$O(B" means hello in Japanese.It's unicode literal.)
In normal Interpreter ( running in console)
u'\\u3053\\u3093\\u306b\\u3061\\u306f'u"$B$3$s$K$A$O(B"
I found a solution.
I posted here.But I found it was closed after I posted.
http://en.wikipedia.org/wiki/Whac-A-Mole
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
IDLE-dev mailing list
IDLE-dev@python.org
http://mail.python.org/mailman/listinfo/idle-dev