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.

diff --git a/Doc/whatsnew/2.6.rst b/Doc/whatsnew/2.6.rst
index df746e793194c42089e0e5f1561fb56b291b82d0..0539a442077da7d9f16eadd5b93a67a80fab6ef9 100644 (file)
--- 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