From ead60e5d1c24f4bd2f53b7994d4240735cc11453 Mon Sep 17 00:00:00 2001 From: Thomas Heller Date: Fri, 6 Dec 2002 22:42:13 +0000 Subject: [PATCH] Typo: propogate -> propagate Bugfix candidate. --- Doc/api/exceptions.tex | 2 +- Doc/api/init.tex | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/api/exceptions.tex b/Doc/api/exceptions.tex index d6c6c7bfdd4..9a5d7d080c6 100644 --- a/Doc/api/exceptions.tex +++ b/Doc/api/exceptions.tex @@ -19,7 +19,7 @@ holds (such as object references or memory allocations); it should \emph{not} continue normally if it is not prepared to handle the error. If returning due to an error, it is important to indicate to the caller that an error has been set. If the error is not handled or -carefully propogated, additional calls into the Python/C API may not +carefully propagated, additional calls into the Python/C API may not behave as intended and may fail in mysterious ways. The error indicator consists of three Python objects corresponding to diff --git a/Doc/api/init.tex b/Doc/api/init.tex index ba16b3c6dba..f748c31b603 100644 --- a/Doc/api/init.tex +++ b/Doc/api/init.tex @@ -657,7 +657,7 @@ interpreter lock has been created. state information. Each extension should use a unique key to use to store state in the dictionary. If this function returns \NULL, an exception has been raised and the caller should allow it to - propogate. + propagate. \end{cfuncdesc} @@ -715,7 +715,7 @@ previous versions. processed after which the exception becomes set within the frame being executed. The effect of this is that as exception propogation causes the Python stack to unwind, the callback is called upon - return to each frame as the exception propogates. Only trace + return to each frame as the exception propagates. Only trace functions receives these events; they are not needed by the profiler. \end{cvardesc}