On 09/12/2010 05:57, Alexander Belopolsky wrote:
On Thu, Dec 9, 2010 at 12:47 AM, Martin v. Löwismar...@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
Am 09.12.2010 06:57, schrieb Alexander Belopolsky:
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
On Wed, Dec 8, 2010 at 6:56 PM, MRAB pyt...@mrabarnett.plus.com wrote:
Is this change intentional? If so, why does unicodeobject.h still do
the mapping?
In 3.2b1, unicodeobject.h doesn't map _PyUnicode_IsWhitespace:
On 09/12/2010 23:35, Daniel Stutzbach wrote:
On Wed, Dec 8, 2010 at 6:56 PM, MRAB pyt...@mrabarnett.plus.com
mailto:pyt...@mrabarnett.plus.com wrote:
Is this change intentional? If so, why does unicodeobject.h still do
the mapping?
In 3.2b1, unicodeobject.h doesn't map
The regex module calls _PyUnicode_IsWhitespace, which is mapped by
unicodeobject.h to either _PyUnicodeUCS2_IsWhitespace or
_PyUnicodeUCS4_IsWhitespace.
From Python 2.5 to Python 3.1 the library pythonXX.lib contains either
_PyUnicodeUCS2_IsWhitespace or _PyUnicodeUCS4_IsWhitespace.
However, in
Am 09.12.2010 03:56, schrieb MRAB:
The regex module calls _PyUnicode_IsWhitespace, which is mapped by
unicodeobject.h to either _PyUnicodeUCS2_IsWhitespace or
_PyUnicodeUCS4_IsWhitespace.
From Python 2.5 to Python 3.1 the library pythonXX.lib contains either
_PyUnicodeUCS2_IsWhitespace or
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