Jed Brown <[email protected]> writes:

I still don't understand the actual problem. I reproduced this funny thing where Python prints 'gcc' and a stack trace without stating an exception, but I didn't figure out what the exception was or why the reporting was messed up.

It turns out that user dict behavior was only added in Python-2.5, so __missing__ was not invoked as expected. Pushed the fix to 'next'. Dave, can you try using 'next'?