Robey Pointer wrote: > On 29 Sep 2005, at 12:06, Steven Bethard wrote: > > >>On 9/29/05, Robey Pointer <robey at lag.net> wrote: >> >> >>>Yesterday I ran into a bug in the C API docs. The top of this page: >>> >>> http://docs.python.org/api/unicodeObjects.html >>> >>>says: >>> >>>Py_UNICODE >>> This type represents a 16-bit unsigned storage type which is >>>used by Python internally as basis for holding Unicode ordinals. On >>>platforms where wchar_t is available and also has 16-bits, Py_UNICODE >>>is a typedef alias for wchar_t to enhance native platform >>>compatibility. On all other platforms, Py_UNICODE is a typedef alias >>>for unsigned short. >>> >> >>I believe this is the same issue that was brought up in May[1]. My >>impression was that people could not agree on a documentation patch. FYI, I've fixed the Py_UNICODE description now. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Oct 10 2005) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! ::::
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4