On Sun, 2006-03-26 at 19:59 +0200, "Martin v. Löwis" wrote: > If it is similar to PyDict_Next, it will have PyObject** /input/ > variables, which are really meant as PyObject* /output/ variables.
Yep, that's exactly what my posted patch does. > For the caller, a clear usage strategy follows from this: either discard > the references before making a potentially-mutating call, or Py_INCREF > the set element before making that mutating call. Yep. Nice and simple. And if you're not making a potentially-mutating call, you don't have to worry about even that. These /are/ valid use cases. -Barry
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
