This is getting better with each Python release. AFAIK, there are only
about 3 or 4 places in the code that do the fprintf(stderr,...) thing -
usually followed by an abort().
Even this code seems to be moving towards a generic abort function (cant
remember the name) so an application should be able to override the abort
function at link time.
In my expericene imbedding Python, I have only seen such errors very few
times - stuffing reference counts is a pretty good way to get them. I have
never seen such an error message from bad Python code - just bad C code
wrapped around Python.
Basically I am saying that explicitely grabbing stderr is a good idea, but
probably not worth it for the number of times anything will be written to
it.
Mark.