From: Benjamin Peterson <benjamin@python.org>
Date: Tue, 15 Jan 2013 21:49:22 +0000 (-0500)
Subject: remove warning about tb circular reference (closes #7340)
X-Git-Tag: v3.3.1rc1~351
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0ad344a8322a7c69b099e25c203d675a5ea3b60d;p=python

remove warning about tb circular reference (closes #7340)
---

diff --git a/Doc/library/sys.rst b/Doc/library/sys.rst
index 93273c4568..626443727d 100644
--- a/Doc/library/sys.rst
+++ b/Doc/library/sys.rst
@@ -215,21 +215,6 @@ always available.
    a traceback object (see the Reference Manual) which encapsulates the call
    stack at the point where the exception originally occurred.
 
-   .. warning::
-
-      Assigning the *traceback* return value to a local variable in a function
-      that is handling an exception will cause a circular reference.  Since most
-      functions don't need access to the traceback, the best solution is to use
-      something like ``exctype, value = sys.exc_info()[:2]`` to extract only the
-      exception type and value.  If you do need the traceback, make sure to
-      delete it after use (best done with a :keyword:`try`
-      ... :keyword:`finally` statement) or to call :func:`exc_info` in a
-      function that does not itself handle an exception.
-
-      Such cycles are normally automatically reclaimed when garbage collection
-      is enabled and they become unreachable, but it remains more efficient to
-      avoid creating cycles.
-
 
 .. data:: exec_prefix