[Python-Dev] Hmmm... __PyObject_NextNotImplemented when tracing lines (original) (raw)

Alexander Belopolsky alexander.belopolsky at gmail.com
Mon Jan 19 18:23:59 CET 2009

On Mon, Jan 19, 2009 at 11:51 AM, <skip at pobox.com> wrote:

I see output like this in several tests on my Mac:

_testarray skipped -- dlopen(/Users/skip/src/python/trunk/build/lib.macosx-10.3-i386-2.7/cPickle.so, 2): Symbol not found: PyObjectNextNotImplemented Referenced from: /Users/skip/src/python/trunk/build/lib.macosx-10.3-i386-2.7/cPickle.so Expected in: dynamic lookup This is in an up-to-date trunk sandbox running ./python.exe Lib/test/regrtest.py -T -D cover ..

I cannot reproduce this on my Mac. It looks like you may have an out of date python.exe in your sandbox. Please check that

$ nm python.exe | grep PyObject_NextNotImplemented 00052940 T __PyObject_NextNotImplemented

has a "T" in the second column.

Note that this symbol seem to have been added recently:

$ svn blame -v Objects/object.c .. 68560 amaury.forgeotdarc 2009-01-12 18:36:55 -0500 (Mon, 12 Jan 2009) _PyObject_NextNotImplemented(PyObject *self) 68560 amaury.forgeotdarc 2009-01-12 18:36:55 -0500 (Mon, 12 Jan 2009) { 68560 amaury.forgeotdarc 2009-01-12 18:36:55 -0500 (Mon, 12 Jan 2009) PyErr_Format(PyExc_TypeError, 68560 amaury.forgeotdarc 2009-01-12 18:36:55 -0500 (Mon, 12 Jan 2009) "'%.200s' object is not iterable", 68560 amaury.forgeotdarc 2009-01-12 18:36:55 -0500 (Mon, 12 Jan 2009) Py_TYPE(self)->tp_name); 68560 amaury.forgeotdarc 2009-01-12 18:36:55 -0500 (Mon, 12 Jan 2009) return NULL; 68560 amaury.forgeotdarc 2009-01-12 18:36:55 -0500 (Mon, 12 Jan 2009) } 68560 amaury.forgeotdarc 2009-01-12 18:36:55 -0500 (Mon, 12 Jan 2009) ..

So it is possible that you did not pick it up in your build yet.

I am puzzled, however, that you don't see problems in a non-coverage run.

More information about the Python-Dev mailing list