diff Modules/parsermodule.c @ 14346:5397fdf88ec2 legacy-trunk

Do the absolute minimal amount of modifications to eradicate Py_FatalError() from module initialization functions. The importing mechanism already checks for PyErr_Occurred() after module importation and it Does The Right Thing. Unfortunately, the following either were not compiled or tested by the regression suite, due to issues with my development platform: almodule.c cdmodule.c mpzmodule.c puremodule.c timingmodule.c
author Barry Warsaw <barry@python.org>
date Fri, 01 Sep 2000 09:01:32 +0000
parents 2c3283094311
children 6f6f965c5e2d
line wrap: on
line diff
--- a/Modules/parsermodule.c	Fri Sep 01 08:10:08 2000 +0000
+++ b/Modules/parsermodule.c	Fri Sep 01 09:01:32 2000 +0000
@@ -2862,11 +2862,10 @@
         parser_error = PyErr_NewException("parser.ParserError", NULL, NULL);
 
     if ((parser_error == 0)
-        || (PyDict_SetItemString(dict, "ParserError", parser_error) != 0)) {
-        /*
-         *  This is serious.
-         */
-        Py_FatalError("can't define parser.ParserError");
+        || (PyDict_SetItemString(dict, "ParserError", parser_error) != 0))
+    {
+	    /* caller will check PyErr_Occurred() */
+	    return;
     }
     /*
      *  Nice to have, but don't cry if we fail.