[Python-Dev] Unicode literals in Python 2.7
v+python at g.nevcal.com
Mon May 11 22:38:29 CEST 2015
On 5/11/2015 1:09 AM, Nick Coghlan wrote:
> On 10 May 2015 at 23:28, Adam Bartoš <drekin at gmail.com> wrote:
>> Glenn Linderman wrote:
>>> Is this going to get released in 3.5, I hope? Python 3 is pretty
>>> limited without some solution for Unicode on the console... probably the
>>> biggest deficiency I have found in Python 3, since its introduction. It
>>> has great Unicode support for files and processing, which convinced me
>>> to switch from Perl, and I like so much else about it, that I can hardly
>>> code in Perl any more (I still support a few Perl programs, but have
>>> ported most of them to Python).
>> I'd love to see it included in 3.5, but I doubt that will happen. For one
>> thing, it's only two weeks till beta 1, which is feature freeze. And mainly,
>> my package is mostly hacking into existing Python environment. A proper
>> implementation would need some changes in Python someone would have to do.
>> See for example my proposal http://bugs.python.org/issue17620#msg234439. I'm
>> not competent to write a patch myself and I have also no feedback to the
>> proposed idea. On the other hand, using the package is good enough for me so
>> I didn't further bring attention to the proposal.
> Right, and while I'm interested in seeing this improved, I'm not
> especially familiar with the internal details of our terminal
> interaction implementation, and even less so when it comes to the
> Windows terminal. Steve Dower's also had his hands full working on the
> Windows installer changes, and several of our other Windows folks
> aren't C programmers.
> PEP 432 (the interpreter startup sequence improvements) will be back
> on the agenda for Python 3.6, so the 3.6 time frame seems more
> plausible at this point.
Wow! Another bug that'll reach a decade in age before being fixed...
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev