On Thu, Dec 9, 2010 at 12:47 AM, "Martin v. Löwis" <mar...@v.loewis.de> wrote: .. >> However, in Python 3.2b1 the library python32.lib contains only >> _PyUnicode_IsWhitespace, therefore breaking the build. >> >> Is this change intentional? If so, why does unicodeobject.h still do >> the mapping? > > Are you sure about this? It's not intentional (except in the limited ABI).
this does seem to be intentional: $ svn log -r 84177 ------------------------------------------------------------------------ r84177 | amaury.forgeotdarc | 2010-08-18 16:44:58 -0400 (Wed, 18 Aug 2010) | 9 lines #5127: Even on narrow unicode builds, the C functions that access the Unicode Database (Py_UNICODE_TOLOWER, Py_UNICODE_ISDECIMAL, and others) now accept and return characters from the full Unicode range (Py_UCS4). The differences from Python code are few: - unicodedata.numeric(), unicodedata.decimal() and unicodedata.digit() now return the correct value for large code points - repr() may consider more characters as printable. ------------------------------------------------------------------------ http://svn.python.org/view?view=rev&revision=84177 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
