➜

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 ncoghlan
Recipients Arfrever, georg.brandl, loewis, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner
Date 2012-08-19.12:59:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7fwsK-9ZRMqKpESDq-ivzshCsKjfEe+-Bu4=V0EGajVEg@mail.gmail.com>
In-reply-to <1345376741.3379.0.camel@localhost.localdomain>
Content 
I guess the analogy with bytes objects is that UCS-2 code points can be
handled as 16-bit integer objects.

If we're going to do a programmatic deprecation now, that's the only
alternative typecode currently available. Do we want to recommend that? Or
do we want to postpone programmatic deprecation until we add a 2-byte code
point type code for 3.4?
History
Date User Action Args
2012-08-19 12:59:24ncoghlansetrecipients: + ncoghlan, loewis, georg.brandl, mark.dickinson, pitrou, vstinner, Arfrever, skrah, meador.inge, python-dev
2012-08-19 12:59:03ncoghlanlinkissue13072 messages
2012-08-19 12:59:03ncoghlancreate