From: Neal Norwitz <nnorwitz@gmail.com>
Date: Fri, 7 Feb 2003 02:27:36 +0000 (+0000)
Subject: Fix SF bug #675259, os.environ leaks under FreeBSD and Mac OS X
X-Git-Tag: v2.3c1~1977
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2b09bc4d571c29ff044d9170156a89e77adb8f61;p=python

Fix SF bug #675259, os.environ leaks under FreeBSD and Mac OS X

Even with the extra work to cleanup the env, *BSD still leaks.  Add a note.

Will backport.
---

diff --git a/Doc/lib/libos.tex b/Doc/lib/libos.tex
index aa57217832..70da201aa5 100644
--- a/Doc/lib/libos.tex
+++ b/Doc/lib/libos.tex
@@ -93,7 +93,9 @@ platforms), and is equivalent to \code{getenv("HOME")} in C.
 If the platform supports the \function{putenv()} function, this
 mapping may be used to modify the environment as well as query the
 environment.  \function{putenv()} will be called automatically when
-the mapping is modified.
+the mapping is modified.  \note{On some platforms, including
+FreeBSD and Mac OS X, setting \code{environ} may cause memory leaks.
+Refer to the system documentation for putenv.}
 
 If \function{putenv()} is not provided, this mapping may be passed to
 the appropriate process-creation functions to cause child processes to
@@ -193,6 +195,10 @@ started with \function{os.system()}, \function{popen()} or
 \function{fork()} and \function{execv()}.
 Availability: most flavors of \UNIX, Windows.
 
+\note{On some platforms, including FreeBSD and Mac OS X,
+setting \code{environ} may cause memory leaks.
+Refer to the system documentation for putenv.}
+
 When \function{putenv()} is
 supported, assignments to items in \code{os.environ} are automatically
 translated into corresponding calls to \function{putenv()}; however,