On 27 August 2014 01:23, Paul Moore <p.f.mo...@gmail.com> wrote: > On 24 August 2014 04:27, Nick Coghlan <ncogh...@gmail.com> wrote: >> One of those areas is the fact that we still use the old 8-bit APIs to >> interact with the Windows console. Those are just as broken in a >> multilingual world as the other Windows 8-bit APIs, so Drekin came up >> with a project to expose the Windows console as a UTF-16-LE stream >> that uses the 16-bit APIs instead: >> https://pypi.python.org/pypi/win_unicode_console >> >> I personally hope we'll be able to get the issues Drekin references >> there resolved for Python 3.5 - if other folks hope for the same >> thing, then one of the best ways to help that happen is to try out the >> win_unicode_console module and provide feedback on what does and >> doesn't work. > > This looks very cool, and I plan on giving it a try. But I don't see > any issues mentioned there (unless you mean the fact that it's not > possible to hook into Python's interactive interpreter directly, but I > don't see how that could be fixed in an external module). There's no > open issues on the project's github tracker.
There are two links to CPython issues from the project description: http://bugs.python.org/issue1602 http://bugs.python.org/issue17620 Part of the feedback on those was that as much as possible should be made available as a third party module before returning to the question of how to update CPython. If we can get additional confirmation that the module addresses the CLI integration issues, then we can take a closer look at switching CPython itself over. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
