From 7b1e917e419c234627a88319cc30d10844d12039 Mon Sep 17 00:00:00 2001 From: "Andrew M. Kuchling" Date: Tue, 15 Jan 2008 14:38:05 +0000 Subject: [PATCH] Restore description of sys.dont_write_bytecode. The duplication is intentional -- this paragraph is in a section describing additions to the sys module, and there's a later section that mentions the switch. I think most people scan the what's-new and don't read it in detail, so a bit of duplication is OK. --- Doc/whatsnew/2.6.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Doc/whatsnew/2.6.rst b/Doc/whatsnew/2.6.rst index df746e7931..0539a44207 100644 --- a/Doc/whatsnew/2.6.rst +++ b/Doc/whatsnew/2.6.rst @@ -1015,6 +1015,17 @@ complete list of changes, or look through the CVS logs for all the details. .. Patch 1534 + Another new variable, :attr:`dont_write_bytecode`, controls whether Python + writes any :file:`.pyc` or :file:`.pyo` files on importing a module. + If this variable is true, the compiled files are not written. The + variable is initially set on start-up by supplying the :option:`-B` + switch to the Python interpreter, or by setting the + :envvar:`PYTHONDONTWRITEBYTECODE` environment variable before + running the interpreter. Python code can subsequently + change the value of this variable to control whether bytecode files + are written or not. + (Contributed by Neal Norwitz and Georg Brandl.) + Information about the command-line arguments supplied to the Python interpreter are available as attributes of a ``sys.flags`` named tuple. For example, the :attr:`verbose` attribute is true if Python -- 2.50.1