This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author inigoserna
Recipients cben, gpolo, inigoserna
Date 2009-08-26.15:47:53
SpamBayes Score 0.00020774236
Marked as misclassified No
Message-id <1251301675.56.0.708897695595.issue6755@psf.upfronthosting.co.za>
In-reply-to
Content
Q. Why not change getch() to always use get_wch()?

This could break backwards compatibility.
There are some code out there that may use getch() to get the bytes
stream one by one and build the wide char.
In fact I'm using this trick to get unicode chars by now.
Look the thread link in first comment to find the implementation I've
developed for my app. Other people are using similar approaches too.


Q. I think you also want fix getkey() / introduce get_wkey().

In my own experience get_wkey isn't be as useful when dealing with wide
chars. But, of course, that's only my use cases.
History
Date User Action Args
2009-08-26 15:47:55inigosernasetrecipients: + inigoserna, cben, gpolo
2009-08-26 15:47:55inigosernasetmessageid: <1251301675.56.0.708897695595.issue6755@psf.upfronthosting.co.za>
2009-08-26 15:47:54inigosernalinkissue6755 messages
2009-08-26 15:47:54inigosernacreate