summaryrefslogtreecommitdiffstats
path: root/Modules/timingmodule.c
diff options
context:
space:
mode:
authorBarry Warsaw <barry@python.org>2000-09-01 09:01:32 (GMT)
committerBarry Warsaw <barry@python.org>2000-09-01 09:01:32 (GMT)
commit9bfd2bf5ede8e5d58775180d6867d81ddcdd3594 (patch)
treecd3adf2b98bc2c0b94980df1953ae9709f46cc28 /Modules/timingmodule.c
parent72dacb80262b73a833802c0b0e5941b8cdb1d79c (diff)
downloadcpython-9bfd2bf5ede8e5d58775180d6867d81ddcdd3594.zip
cpython-9bfd2bf5ede8e5d58775180d6867d81ddcdd3594.tar.gz
cpython-9bfd2bf5ede8e5d58775180d6867d81ddcdd3594.tar.bz2
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
Diffstat (limited to 'Modules/timingmodule.c')
-rw-r--r--Modules/timingmodule.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/Modules/timingmodule.c b/Modules/timingmodule.c
index 0742005..1844696 100644
--- a/Modules/timingmodule.c
+++ b/Modules/timingmodule.c
@@ -72,6 +72,4 @@ static PyMethodDef timing_methods[] = {
DL_EXPORT(void) inittiming(void)
{
(void)Py_InitModule("timing", timing_methods);
- if (PyErr_Occurred())
- Py_FatalError("can't initialize module timing");
}