From: Mark Hammond <mhammond@skippinet.com.au>
Date: Mon, 17 Oct 2011 00:28:09 +0000 (+1100)
Subject: Issue #7833: Ext. modules built using distutils on Windows no longer get a manifest
X-Git-Tag: v3.3.0a1~1155
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a9efb6fdd8f102eb1217cb93fccd477a82e1cc2f;p=thirdparty%2FPython%2Fcpython.git

Issue #7833: Ext. modules built using distutils on Windows no longer get a manifest
---

a9efb6fdd8f102eb1217cb93fccd477a82e1cc2f
diff --cc Misc/NEWS
index f490a7a1080c,029f16ca54d3..b8d43bafc7ce
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@@ -10,10 -10,10 +10,14 @@@ What's New in Python 3.3 Alpha 1
  Core and Builtins
  -----------------
  
+ - Issue #7833: Extension modules built using distutils on Windows will no
+   longer include a "manifest" to prevent them failing at import time in some
+   embedded situations.
+ 
 +- PEP 3151 / issue #12555: reworking the OS and IO exception hierarchy.
 +
 +- Add internal API for static strings (_Py_identifier et al.).
 +
  - Issue #13063: the Windows error ERROR_NO_DATA (numbered 232 and described
    as "The pipe is being closed") is now mapped to POSIX errno EPIPE
    (previously EINVAL).