From: Antoine Pitrou <solipsis@pitrou.net>
Date: Sat, 17 Nov 2012 22:29:28 +0000 (+0100)
Subject: Issue #16215: Fix potential double memory free in str.replace().
X-Git-Tag: v3.4.0a1~1990
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5439458a2a5f4da38eeef2007f400152148fe04f;p=python

Issue #16215: Fix potential double memory free in str.replace().
Patch by Serhiy Storchaka.
---

5439458a2a5f4da38eeef2007f400152148fe04f
diff --cc Misc/NEWS
index aa9f6c7550,b68ead6f9f..df8f014a43
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@@ -10,15 -12,9 +10,18 @@@ What's New in Python 3.4.0 Alpha 1
  Core and Builtins
  -----------------
  
+ - Issue #16215: Fix potential double memory free in str.replace().  Patch
+   by Serhiy Storchaka.
+ 
 +- Issue #16290: A float return value from the __complex__ special method is no
 +  longer accepted in the complex() constructor.
 +
 +- Issue #16416: On Mac OS X, operating system data are now always
 +  encoded/decoded to/from UTF-8/surrogateescape, instead of the locale encoding
 +  (which may be ASCII if no locale environment variable is set), to avoid
 +  inconsistencies with os.fsencode() and os.fsdecode() functions which are
 +  already using UTF-8/surrogateescape.
 +
  - Issue #16453: Fix equality testing of dead weakref objects.
  
  - Issue #9535: Fix pending signals that have been received but not yet