diff options
author | Terry Jan Reedy <tjreedy@udel.edu> | 2016-05-02 22:30:19 (GMT) |
---|---|---|
committer | Terry Jan Reedy <tjreedy@udel.edu> | 2016-05-02 22:30:19 (GMT) |
commit | 478be14ec0a2ae44e6ab78ed79ea8d238581a4d2 (patch) | |
tree | ed7d20524d62f972313ca9ada9c550afa31822f2 | |
parent | 7a5842e1986847da2e0012b8388511b6cbbd727d (diff) | |
parent | 929d7f86d50b21ac10ad7fea73d3b9c4cf63b18a (diff) | |
download | cpython-478be14ec0a2ae44e6ab78ed79ea8d238581a4d2.zip cpython-478be14ec0a2ae44e6ab78ed79ea8d238581a4d2.tar.gz cpython-478be14ec0a2ae44e6ab78ed79ea8d238581a4d2.tar.bz2 |
Merge with 3.5
-rw-r--r-- | Doc/library/idle.rst | 18 | ||||
-rw-r--r-- | Lib/idlelib/help.html | 22 |
2 files changed, 22 insertions, 18 deletions
diff --git a/Doc/library/idle.rst b/Doc/library/idle.rst index df08fe8..2140e85 100644 --- a/Doc/library/idle.rst +++ b/Doc/library/idle.rst @@ -550,14 +550,16 @@ IDLE-console differences As much as possible, the result of executing Python code with IDLE is the same as executing the same code in a console window. However, the different -interface and operation occasionally affects results. - -For instance, IDLE normally executes user code in a separate process from -the IDLE GUI itself. The IDLE versions of sys.stdin, .stdout, and .stderr in the -execution process get input from and send output to the GUI process, -which keeps control of the keyboard and screen. This is normally transparent, -but code that access these object will see different attribute values. -Also, functions that directly access the keyboard and screen will not work. +interface and operation occasionally affects visible results. For instance, +``sys.modules`` starts with more entries. + +IDLE also replaces ``sys.stdin``, ``sys.stdout``, and ``sys.stderr`` with +objects that get input from and send output to the Shell window. +When this window has the focus, it controls the keyboard and screen. +This is normally transparent, but functions that directly access the keyboard +and screen will not work. If ``sys`` is reset with ``importlib.reload(sys)``, +IDLE's changes are lost and things li ke ``input``, ``raw_input``, and +``print`` will not work correctly. With IDLE's Shell, one enters, edits, and recalls complete statements. Some consoles only work with a single physical line at a time. diff --git a/Lib/idlelib/help.html b/Lib/idlelib/help.html index 3823613..ec0b218 100644 --- a/Lib/idlelib/help.html +++ b/Lib/idlelib/help.html @@ -163,7 +163,7 @@ be undone.</dd> <dt>Find Selection</dt> <dd>Search for the currently selected string, if there is one.</dd> <dt>Find in Files...</dt> -<dd>Open a file search dialog. Put results in an new output window.</dd> +<dd>Open a file search dialog. Put results in a new output window.</dd> <dt>Replace...</dt> <dd>Open a search-and-replace dialog.</dd> <dt>Go to Line</dt> @@ -517,13 +517,15 @@ set in the Options dialog.</li> <h3>25.5.3.2. IDLE-console differences<a class="headerlink" href="#idle-console-differences" title="Permalink to this headline">ΒΆ</a></h3> <p>As much as possible, the result of executing Python code with IDLE is the same as executing the same code in a console window. However, the different -interface and operation occasionally affects results.</p> -<p>For instance, IDLE normally executes user code in a separate process from -the IDLE GUI itself. The IDLE versions of sys.stdin, .stdout, and .stderr in the -execution process get input from and send output to the GUI process, -which keeps control of the keyboard and screen. This is normally transparent, -but code that access these object will see different attribute values. -Also, functions that directly access the keyboard and screen will not work.</p> +interface and operation occasionally affects visible results. For instance, +<code class="docutils literal"><span class="pre">sys.modules</span></code> starts with more entries.</p> +<p>IDLE also replaces <code class="docutils literal"><span class="pre">sys.stdin</span></code>, <code class="docutils literal"><span class="pre">sys.stdout</span></code>, and <code class="docutils literal"><span class="pre">sys.stderr</span></code> with +objects that get input from and send output to the Shell window. +When this window has the focus, it controls the keyboard and screen. +This is normally transparent, but functions that directly access the keyboard +and screen will not work. If <code class="docutils literal"><span class="pre">sys</span></code> is reset with <code class="docutils literal"><span class="pre">importlib.reload(sys)</span></code>, +IDLE’s changes are lost and things li ke <code class="docutils literal"><span class="pre">input</span></code>, <code class="docutils literal"><span class="pre">raw_input</span></code>, and +<code class="docutils literal"><span class="pre">print</span></code> will not work correctly.</p> <p>With IDLE’s Shell, one enters, edits, and recalls complete statements. Some consoles only work with a single physical line at a time.</p> </div> @@ -694,12 +696,12 @@ are currently:</p> </ul> </div> <div class="footer"> - © <a href="../copyright.html">Copyright</a> 1990-2016, Python Software Foundation. + © <a href="../copyright.html">Copyright</a> 2001-2016, Python Software Foundation. <br /> The Python Software Foundation is a non-profit corporation. <a href="https://www.python.org/psf/donations/">Please donate.</a> <br /> - Last updated on Feb 29, 2016. + Last updated on May 02, 2016. <a href="../bugs.html">Found a bug</a>? <br /> Created using <a href="http://sphinx.pocoo.org/">Sphinx</a> 1.3.3. |