The hash randomization change conflates 'pydebug' builds (which define the 'Py_DEBUG' preprocessor symbol) and asserts (which use 'NDEBUG' instead.) While Py_DEBUG automatically unsets NDEBUG, the inverse is not true (and should not be true.)

In random.c (and Include/object.h), _Py_HashSecret_Initialized is defined as static or global depending on the value of Py_DEBUG. But in (at least) Objects/stringobject.c and Objects/unicodeobject.c, unguarded asserts are used that check the value of _Py_HashSecret_Initialized. This causes builds that define neither NDEBUG nor Py_DEBUG to fail. Either the guard used around the declaration and definition should be '#ifndef NDEBUG' instead of '#ifdef Py_DEBUG', or there should be a Py_DEBUG guard around the two assert statements.

(I would submit a patch but my development environment died during a nasty power outage yesterday.)

New changeset a11a2bbd8241 by Benjamin Peterson in branch '2.7':
fix build without Py_DEBUG and DNDEBUG (closes #14509)
http://hg.python.org/cpython/rev/a11a2bbd8241

New changeset 64bb1d258322 by Benjamin Peterson in branch '3.1':
fix build without Py_DEBUG and DNDEBUG (closes #14509)
http://hg.python.org/cpython/rev/64bb1d258322

New changeset 5168483316b5 by Benjamin Peterson in branch '3.2':
merge 3.1 (#14509)
http://hg.python.org/cpython/rev/5168483316b5

New changeset c20f604a2da6 by Benjamin Peterson in branch 'default':
merge 3.2 (#14509)
http://hg.python.org/cpython/rev/c20f604a2da6