#3668: When PyArg_ParseTuple correctly parses a s* format, but raises an
exception afterwards (for a subsequent parameter), the user code will
not call PyBuffer_Release() and memory will leak.
Reviewed by Amaury Forgeot d'Arc.
diff --git a/Misc/NEWS b/Misc/NEWS
index 822d1c9..34fbd69 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -12,6 +12,10 @@
Core and Builtins
-----------------
+- Issue #3668: Fix a memory leak with the "s*" argument parser in
+ PyArg_ParseTuple and friends, which occurred when the argument for "s*"
+ was correctly parsed but parsing of subsequent arguments failed.
+
- Issue #2534: speed up isinstance() and issubclass() by 50-70%, so as to
match Python 2.5 speed despite the __instancecheck__ / __subclasscheck__
mechanism. In the process, fix a bug where isinstance() and issubclass(),