[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-08-20 Thread irdb
Changes by irdb dalba.w...@gmail.com: -- nosy: +irdb ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17348 ___ ___ Python-bugs-list mailing list

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-22 Thread Serhiy Storchaka
Changes by Serhiy Storchaka storch...@gmail.com: -- resolution: - duplicate superseder: - IDLE console uses incorrect encoding. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17348 ___

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-22 Thread R. David Murray
R. David Murray added the comment: Serhiy has proposed a patch on the older issue, closing this one since it is a duplicate. -- stage: - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars

2013-04-21 Thread Tomoki Imai
Tomoki Imai added the comment: NO,this thread should not be closed! This is IDLE Bug.I found, IDLE has issue in using unicode literal. In normal interpreter in console. uこんにちは u'\u3053\u3093\u306b\u3061\u306f' In IDLE. uこんにちは u'\xe3\x81\x93\xe3\x82\x93\xe3\x81\xab\xe3\x81\xa1\xe3\x81\xaf' I

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars

2013-04-21 Thread R. David Murray
R. David Murray added the comment: I believe you have indeed understood what the original poster was reporting. However, those lines date back a long time (2002 or earlier). They exist in Python2 only, and there they have a purpose, so they can't just be deleted. My guess is the problem is a

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-21 Thread R. David Murray
Changes by R. David Murray rdmur...@bitdance.com: -- title: Unicode - encoding seems to be lost for inputs of unicode chars - Unicode - encoding seems to be lost for inputs of unicode chars in IDLE ___ Python tracker rep...@bugs.python.org

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-21 Thread Tomoki Imai
Tomoki Imai added the comment: Thanks. I noticed Terry used python3 to confirm this problem... I am Japanese, but using English environment. Here is my locale settings. And I'm using Linux. konomi:tomoki% locale LANG=en_US.utf8 LC_CTYPE=en_US.UTF-8

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-21 Thread R. David Murray
R. David Murray added the comment: Well, it does seem to me that there is something wrong here. Your fix may even be correct, but I'd hesitate to apply it without someone understanding why those lines were added in the first place. (I *think* they were added by Martin von Loewis, but I'm

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-21 Thread Terry J. Reedy
Terry J. Reedy added the comment: When discussing problematical behavior, one should specify OS and exact Python version, including bugfix number. If at all possible, one should use the latest bugfix release with all released bugfixes. 2.7.3 came out 10+ months before the original report. I

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-21 Thread Tomoki Imai
Tomoki Imai added the comment: Sorry.I forgot to note my environment. I'm using Arch Linux. $ uname -a Linux manaka 3.8.7-1-ARCH #1 SMP PREEMPT Sat Apr 13 09:01:47 CEST 2013 x86_64 GNU/Linux And python version is here. $ python --version Python 2.7.4 IDLE's version is same, 2.7.4 downloaded

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-21 Thread Ned Deily
Ned Deily added the comment: I think this is another case where confusion is introduced by the behavior of Python 2 interactive mode with regard to encodings. In 2.x Python/pythonrun.c, depending on a number of factors the interactive loop will try to set a more useful encoding on stdin,

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-21 Thread Ned Deily
Ned Deily added the comment: Also see Issue15809 in which Martin proposed the same patch but then explained why it isn't totally correct. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17348

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-21 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- Removed message: http://bugs.python.org/msg187547 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17348 ___

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars in IDLE

2013-04-21 Thread R. David Murray
R. David Murray added the comment: For those of us without fancy input methods, I was able to see the same problem using a simple non-ascii letter (an accented a: á. You will note that my stdin encoding ought to be utf-8, so I'm not sure why it fails (but I didn't check that). Removing the

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars

2013-03-08 Thread Terry J. Reedy
Terry J. Reedy added the comment: I do not see any bug. Unicode chars do not have an encoding (except internally) The .encode() method encodes the the unicode string to a byte string. It does *not* mutate the string. Since you do not bind the byte string to anything, it disappears. Compare

[issue17348] Unicode - encoding seems to be lost for inputs of unicode chars

2013-03-04 Thread Pradyun Gedam
New submission from Pradyun Gedam: In IDLE, I have spotted a peculiar problem. I have attached an .png file which is a screen capture of 'session' on IDLE. It seems that the Unicode character that has been input, loses its encoding. My 'session' Python 2.7.2 (default, Jun 12 2011, 15:08:59)