Am seeing occasional assertion failures in the garbage collector.
These are typically reference-counting errors _somewhere_ in one of the DSOs linked into the python process, and are thus hard to track down.
See e.g. bug 613917
Arguably we could build without assertions, but this could well turn these errors into segfaults rather than asserts.
I've written a patch that changes these assertions so that they also attempt to print the repr() of the problem object to stderr before aborting, in the hope of better crash reports.
Sent upstream as:
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.