[issue4465] The result of set_copy() is not checked for NULL

Raymond Hettinger <[EMAIL PROTECTED]> added the comment: The code is correct as-is. -- nosy: +rhettinger ___ Python tracker <[EMAIL PROTECTED]> ___

[issue4465] The result of set_copy() is not checked for NULL

Mark Dickinson <[EMAIL PROTECTED]> added the comment: I believe the code is correct as it is. The relevant lines are in set_intersection: if ((PyObject *)so == other) return set_copy(so); If the result of the set_copy is NULL then the NULL is passed directly back to th

[issue4465] The result of set_copy() is not checked for NULL

New submission from Brian Szuter <[EMAIL PROTECTED]>: Python-2.5.2/Objects/setobject.c Line 1204 The result of set_copy() is not checked for NULL. [See Objects/setobject.c(set_difference) for example of correct usage] -- components: None messages: 76606 nosy: CWRU_Researcher1 severity: