[issue1181] Redefine clear() for os.environ to use unsetenv() if possible

Georg Brandl added the comment: Committed, incl. docs, as rev. 58221. -- assignee: -> georg.brandl nosy: +georg.brandl resolution: -> accepted status: open -> closed __ Tracker <[EMAIL PROTECTED]> _

[issue1181] Redefine clear() for os.environ to use unsetenv() if possible

Guido van Rossum added the comment: On 9/20/07, Raghuram Devarakonda <[EMAIL PROTECTED]> wrote: > Shouldn't the first clear() in the patch say "del > self.data[key.upper()]" instead of "del self.data[key]"? I also think > the patch should include doc change. I don't think so -- it goes over self

[issue1181] Redefine clear() for os.environ to use unsetenv() if possible

Raghuram Devarakonda added the comment: Shouldn't the first clear() in the patch say "del self.data[key.upper()]" instead of "del self.data[key]"? I also think the patch should include doc change. __ Tracker <[EMAIL PROTECTED]> _

[issue1181] Redefine clear() for os.environ to use unsetenv() if possible

Guido van Rossum added the comment: Sounds like a good idea. Anyone care to check it in? -- nosy: +gvanrossum __ Tracker <[EMAIL PROTECTED]> __

[issue1181] Redefine clear() for os.environ to use unsetenv() if possible

Changes by Raghuram Devarakonda: -- nosy: +draghuram __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue1181] Redefine clear() for os.environ to use unsetenv() if possible

Changes by Sean Reifschneider: -- keywords: +patch priority: -> normal __ Tracker <[EMAIL PROTECTED]> __ ___ Python-bugs-list mailing list Uns

[issue1181] Redefine clear() for os.environ to use unsetenv() if possible

New submission from Martin Horcicka: This patch makes os.environ.clear() to have the same effect as: for name in os.environ.keys(): del os.environ[name] I believe that most people expect the effects to be the same anyway. The practical benefit is a simpler redefinition of the whole environ