Message168571
| Author |
pitrou |
| Recipients |
Arfrever, georg.brandl, loewis, mark.dickinson, meador.inge, ncoghlan, pitrou, python-dev, skrah, vstinner |
| Date |
2012年08月19日.13:13:57 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1345381851.3379.3.camel@localhost.localdomain> |
| In-reply-to |
<CADiSq7fwsK-9ZRMqKpESDq-ivzshCsKjfEe+-Bu4=V0EGajVEg@mail.gmail.com> |
| 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?
I don't understand. If you want to handle 16-bit integers, you already
have the "h" and "H" type codes. |
|