Logged In: YES
user_id=80475
Guido, please reject this patch.
I laid-out my reasoning in these two posts:
http://mail.python.org/pipermail/python-dev/2006-
March/062652.html
http://mail.python.org/pipermail/python-dev/2006-
March/062737.html
In particular, I've found PySet_Next() to be disasterously
error-prone (and have had to fix several hard-to-find bugs
directly attributable this function). There was some need
for it in the PyDict API because it fetched key and value
pointers at the same time and allowed direct modification
of values. This of course does not apply to sets which do
not have a value field.
The PySet_Clear() function should be PyObject_Clear() like
other functions that have tp_slots. There is no more of a
case for this function than there would be for PySet_Repr,
PySet_Len, PySet_IsTrue, or PySet_Print.
The PySet_Update() function gets in the way of my future
development plans for this module.
None of these functions are necessary. They simply
reflect Barry's programming style and views on having fat,
overly-concrete APIs.
This patch is against my wishes for the module. As the
module author and principal maintainer, if I still have a
say in the module's development, I strongly prefer
rejection of this patch.
|