From: Thomas Heller <theller@ctypes.org>
Date: Fri, 4 Aug 2006 18:17:40 +0000 (+0000)
Subject: On Windows, make PyErr_Warn an exported function again.
X-Git-Tag: v2.5c1~143
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=74d36f0d95d40f7ae70fbc4d695528c8b769d229;p=thirdparty%2FPython%2Fcpython.git

On Windows, make PyErr_Warn an exported function again.
---

diff --git a/Misc/NEWS b/Misc/NEWS
index 5b7830968a6c..a6797f4b8793 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -12,6 +12,9 @@ What's New in Python 2.5 release candidate 1?
 Core and builtins
 -----------------
 
+- On Windows, the PyErr_Warn function is now exported from
+  the Python dll again.
+
 - Bug #1191458: tracing over for loops now produces a line event
   on each iteration.  Fixing this problem required changing the .pyc
   magic number.  This means that .pyc files generated before 2.5c1
diff --git a/Python/errors.c b/Python/errors.c
index 43d89bd9c807..7b7105104ad7 100644
--- a/Python/errors.c
+++ b/Python/errors.c
@@ -664,7 +664,7 @@ PyErr_WarnEx(PyObject *category, const char *message, Py_ssize_t stack_level)
 
 #undef PyErr_Warn
 
-int
+PyAPI_FUNC(int)
 PyErr_Warn(PyObject *category, char *message)
 {
 	return PyErr_WarnEx(category, message, 1);