Commit b5199269 authored by Tim Peters's avatar Tim Peters

Doc and NEWS changes due to Jeremy adding traceback objects to gc.

parent b2c8ef25
...@@ -109,7 +109,10 @@ It is always available. ...@@ -109,7 +109,10 @@ It is always available.
exception type and value. If you do need the traceback, make sure exception type and value. If you do need the traceback, make sure
to delete it after use (best done with a \keyword{try} to delete it after use (best done with a \keyword{try}
... \keyword{finally} statement) or to call \function{exc_info()} in ... \keyword{finally} statement) or to call \function{exc_info()} in
a function that does not itself handle an exception.} a function that does not itself handle an exception.} \note{Beginning
with Python 2.2, such cycles are automatically reclaimed when garbage
collection is enabled and they become unreachable, but it remains more
efficient to avoid creating cycles.}
\end{funcdesc} \end{funcdesc}
\begin{datadesc}{exc_type} \begin{datadesc}{exc_type}
......
...@@ -16,6 +16,10 @@ Extension modules ...@@ -16,6 +16,10 @@ Extension modules
Library Library
- Traceback objects are now scanned by cyclic garbage collection, so
cycles created by casual use of sys.exc_info() no longer cause
permanent memory leaks (provided garbage collection is enabled).
Tools/Demos Tools/Demos
Build Build
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment