with WT internal names. These methods were exposed for conflict because we created public C names by 'extending' classes in SWIG. SWIG's wrapper naming for such methods apparently follows a different convention than the usual "_wrap_<PythonName>_<FunctionName>", and uses "<CTypeName>_<FunctionName", e.g. "__wt_cursor_equals". Refs #1574.