From: Jason R. Coombs <jaraco@jaraco.com>
Date: Wed, 4 May 2016 16:00:32 +0000 (-0400)
Subject: Issue #20120: Merge with 3.5
X-Git-Tag: v3.6.0a1~78
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ad039f754805dc9c9d4cd95ed249984bc1405bd6;p=python

Issue #20120: Merge with 3.5
---

ad039f754805dc9c9d4cd95ed249984bc1405bd6
diff --cc Misc/NEWS
index db22c2b0a0,2993c66331..a8a3e3a4be
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@@ -10,17 -10,12 +10,23 @@@ Release date: tb
  Core and Builtins
  -----------------
  
+ - Issue #20120: Use RawConfigParser for .pypirc parsing,
+   removing support for interpolation unintentionally added
+   with move to Python 3. Behavior no longer does any
+   interpolation in .pypirc files, matching behavior in Python
+   2.7 and Setuptools 19.0.
+ 
 +- Issue #26249: Memory functions of the :c:func:`PyMem_Malloc` domain
 +  (:c:data:`PYMEM_DOMAIN_MEM`) now use the :ref:`pymalloc allocator <pymalloc>`
 +  rather than system :c:func:`malloc`. Applications calling
 +  :c:func:`PyMem_Malloc` without holding the GIL can now crash: use
 +  ``PYTHONMALLOC=debug`` environment variable to validate the usage of memory
 +  allocators in your application.
 +
 +- Issue #26802: Optimize function calls only using unpacking like
 +  ``func(*tuple)`` (no other positional argument, no keyword): avoid copying
 +  the tuple. Patch written by Joe Jevnik.
 +
  - Issue #26659: Make the builtin slice type support cycle collection.
  
  - Issue #26718: super.__init__ no longer leaks memory if called multiple times.