ENH: Using dPython.h to wrap around Python.h. It provides the ability to link against release python with a debug build of your project.

Copied from file "VTK/Common/vtkPython.h" available on http://vtk.org/gitweb

Author: jcfr

src/PythonQtClassWrapper.h

@@ -42,7 +42,7 @@
 */
 //----------------------------------------------------------------------------------
 
-#include <Python.h>
+#include <dPython.h>
 
 #include "PythonQtSystem.h"
 

src/PythonQtImporter.h

@@ -42,7 +42,7 @@
 */
 //----------------------------------------------------------------------------------
 
-#include "Python.h"
+#include "dPython.h"
 #include "structmember.h"
 #include "osdefs.h"
 #include "marshal.h"

src/PythonQtInstanceWrapper.h

@@ -42,7 +42,7 @@
 */
 //----------------------------------------------------------------------------------
 
-#include <Python.h>
+#include <dPython.h>
 
 #include "PythonQtSystem.h"
 #include <QPointer>

src/PythonQtObjectPtr.h

@@ -42,7 +42,7 @@
 */
 //----------------------------------------------------------------------------------
 
-#include <Python.h>
+#include <dPython.h>
 #include "PythonQtSystem.h"
 #include <QVariant>
 #include <QVariantList>

src/PythonQtSignalReceiver.h

@@ -42,7 +42,7 @@
 */
 //----------------------------------------------------------------------------------
 
-#include <Python.h>
+#include <dPython.h>
 #include "PythonQtSystem.h"
 #include "PythonQtObjectPtr.h"
 

src/PythonQtSlot.h

@@ -42,7 +42,7 @@
 */
 //----------------------------------------------------------------------------------
 
-#include "Python.h"
+#include "dPython.h"
 #include "PythonQtSystem.h"
 #include "structmember.h"
 

src/PythonQtStdDecorators.h

@@ -43,7 +43,7 @@
 //----------------------------------------------------------------------------------
 
 #include "PythonQtSystem.h"
-#include <Python.h>
+#include <dPython.h>
 #include <QObject>
 #include <QVariantList>
 #include <QTextDocument>

src/PythonQtStdOut.h

@@ -43,7 +43,7 @@
 //----------------------------------------------------------------------------------
 
 
-#include <Python.h>
+#include <dPython.h>
 #include "structmember.h"
 #include <QString>
 

src/dPython.h

@@ -0,0 +1,61 @@
+/*=========================================================================
+
+  Library:   CTK
+ 
+  Copyright (c) 2010  Kitware Inc.
+
+  Licensed under the Apache License, Version 2.0 (the "License");
+  you may not use this file except in compliance with the License.
+  You may obtain a copy of the License at
+
+      http://www.commontk.org/LICENSE
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+ 
+=========================================================================*/
+/*=========================================================================
+
+  Program:   Visualization Toolkit
+  Module:    vtkPython.h
+
+  Copyright (c) Ken Martin, Will Schroeder, Bill Lorensen
+  All rights reserved.
+  See Copyright.txt or http://www.kitware.com/Copyright.htm for details.
+
+     This software is distributed WITHOUT ANY WARRANTY; without even
+     the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
+     PURPOSE.  See the above copyright notice for more information.
+
+=========================================================================*/
+
+#ifndef __dPython_h
+#define __dPython_h
+
+/* 
+   Use the real python debugging library if it is provided.  
+   Otherwise use the "documented" trick involving checking for _DEBUG
+   and undefined that symbol while we include Python headers.
+   Update: this method does not fool Microsoft Visual C++ 8 anymore; two
+   of its header files (crtdefs.h and use_ansi.h) check if _DEBUG was set
+   or not, and set flags accordingly (_CRT_MANIFEST_RETAIL, 
+   _CRT_MANIFEST_DEBUG, _CRT_MANIFEST_INCONSISTENT). The next time the
+   check is performed in the same compilation unit, and the flags are found,
+   and error is triggered. Let's prevent that by setting _CRT_NOFORCE_MANIFEST.
+*/
+
+#ifdef _DEBUG
+# undef _DEBUG
+# if defined(_MSC_VER) && _MSC_VER >= 1400
+#   define _CRT_NOFORCE_MANIFEST 1
+# endif
+# include <Python.h>
+# define _DEBUG
+#else
+# include <Python.h>
+#endif
+
+#endif