[gedit] Clarify the use of signal overriding instead of Py_InitializeEx

[Jesse van den Kieboom <jessevdk src gnome org>]

commit 99458027b33c443a43910fb9e478826c528ef75c
Author: Jesse van den Kieboom <jessevdk gnome org>
Date:   Mon May 10 14:45:41 2010 +0200

    Clarify the use of signal overriding instead of Py_InitializeEx

 plugin-loaders/python/gedit-plugin-loader-python.c |    7 +++----
 1 files changed, 3 insertions(+), 4 deletions(-)
---
diff --git a/plugin-loaders/python/gedit-plugin-loader-python.c b/plugin-loaders/python/gedit-plugin-loader-python.c
index d6fbbbc..34799eb 100644
--- a/plugin-loaders/python/gedit-plugin-loader-python.c
+++ b/plugin-loaders/python/gedit-plugin-loader-python.c
@@ -554,10 +554,9 @@ gedit_python_init (GeditPluginLoaderPython *loader)
 	loader->priv->status = GEDIT_PYTHON_STATUS_FAILED;
 
 	/* Hack to make python not overwrite SIGINT: this is needed to avoid
-	 * the crash reported on bug #326191 */
-
-	/* CHECK: can't we use Py_InitializeEx instead of Py_Initialize in order
-          to avoid to manage signal handlers ? - Paolo (Dec. 31, 2006) */
+	 * the crash reported on bug #326191. It's actually the signal
+	 * module that overrides SIGINT when it's set to the default,
+	 * so using Py_InitializeEx (0) also does not work */
 
 #ifdef HAVE_SIGACTION
 	/* Save old handler */