Am 09.12.2010 06:57, schrieb Alexander Belopolsky: > On Thu, Dec 9, 2010 at 12:47 AM, "Martin v. Löwis" <martin at 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: Oops, right; I was confusing this issue 8654. Then going back to the OP: Why exactly does that break the build? There should be no problem - you shouldn't see _PyUnicodeUCS2_IsWhitespace anywhere in 3.2. Regards, Martin
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