Antoine Pitrou added the comment: > 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue13072> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
