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

skip at pobox.com skip at pobox.com
Mon Jan 19 17:51:37 CET 2009

• Previous message: [Python-Dev] PEP 3142: Add a "while" clause to generator expressions
• Next message: [Python-Dev] Hmmm... __PyObject_NextNotImplemented when tracing lines
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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

test_array skipped -- dlopen(/Users/skip/src/python/trunk/build/lib.macosx-10.3-i386-2.7/cPickle.so, 2): Symbol not found: __PyObject_NextNotImplemented
  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

Didn't see that in a non-coverage pass. The following tests give this message:

test_exceptions
test_array
test_collections
test_copy_reg
test_cpickle
test_datetime
test_deque
test_fractions
test_logging
test_multiprocessing
test_pickle
test_pickletools
test_re
test_slice
test_xpickle

I see other weirdness as well including a failure of test_sys and the apparent inability to actually write out any useful coverage info, but this is the standout. In general it appears the tracing support in regrtest.py causes a bunch of problems.

Skip

• Previous message: [Python-Dev] PEP 3142: Add a "while" clause to generator expressions
• Next message: [Python-Dev] Hmmm... __PyObject_NextNotImplemented when tracing lines
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Python-Dev mailing list