Mailman 3 November 2018 - Python-checkins

closes bpo-35171: Fix test_TimeRE_recreation_timezone failure on some systems. (GH-10347)
by Miss Islington (bot) 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/ffbce43c1aa457b5976665eb2e47771198… commit: ffbce43c1aa457b5976665eb2e47771198c7af06 branch: 2.7 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: GitHub <noreply(a)github.com> date: 2018-11-05T20:59:07-08:00 summary: closes bpo-35171: Fix test_TimeRE_recreation_timezone failure on some systems. (GH-10347) The test depended on '/usr/share/zoneinfo/posixrules' or equivalent because it set TZ without explicit DST transition rules. At least on OpenSUSE Tumbleweed that file is linked to '/etc/localtime', making the test fail with certain local timezones, such as 'Europe/Moscow' which doesn't have DST transitions since 2011. (cherry picked from commit f1b9ad3d38c11676b45edcbf2369239bae436e56) Co-authored-by: Alexey Izbyshev <izbyshev(a)ispras.ru> files: M Lib/test/test_strptime.py diff --git a/Lib/test/test_strptime.py b/Lib/test/test_strptime.py index 48ad5daec402..a7af85a6d556 100644 --- a/Lib/test/test_strptime.py +++ b/Lib/test/test_strptime.py @@ -580,7 +580,7 @@ def test_TimeRE_recreation_locale(self): finally: locale.setlocale(locale.LC_TIME, locale_info) - @support.run_with_tz('STD-1DST') + @support.run_with_tz('STD-1DST,M4.1.0,M10.1.0') def test_TimeRE_recreation_timezone(self): # The TimeRE instance should be recreated upon changing the timezone. oldtzname = time.tzname

1 0

closes bpo-35171: Fix test_TimeRE_recreation_timezone failure on some systems. (GH-10347)
by Miss Islington (bot) 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/d0e3105f7ca3fc54b167edc756ce545cba… commit: d0e3105f7ca3fc54b167edc756ce545cbab0ce95 branch: 3.6 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: GitHub <noreply(a)github.com> date: 2018-11-05T20:50:04-08:00 summary: closes bpo-35171: Fix test_TimeRE_recreation_timezone failure on some systems. (GH-10347) The test depended on '/usr/share/zoneinfo/posixrules' or equivalent because it set TZ without explicit DST transition rules. At least on OpenSUSE Tumbleweed that file is linked to '/etc/localtime', making the test fail with certain local timezones, such as 'Europe/Moscow' which doesn't have DST transitions since 2011. (cherry picked from commit f1b9ad3d38c11676b45edcbf2369239bae436e56) Co-authored-by: Alexey Izbyshev <izbyshev(a)ispras.ru> files: M Lib/test/test_strptime.py diff --git a/Lib/test/test_strptime.py b/Lib/test/test_strptime.py index 1438487161f9..92de8110bc6d 100644 --- a/Lib/test/test_strptime.py +++ b/Lib/test/test_strptime.py @@ -641,7 +641,7 @@ def test_TimeRE_recreation_locale(self): finally: locale.setlocale(locale.LC_TIME, locale_info) - @support.run_with_tz('STD-1DST') + @support.run_with_tz('STD-1DST,M4.1.0,M10.1.0') def test_TimeRE_recreation_timezone(self): # The TimeRE instance should be recreated upon changing the timezone. oldtzname = time.tzname

1 0

closes bpo-35171: Fix test_TimeRE_recreation_timezone failure on some systems. (GH-10347)
by Miss Islington (bot) 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/ca592bcf56fca93210331327777fe20fde… commit: ca592bcf56fca93210331327777fe20fdeff985a branch: 3.7 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: GitHub <noreply(a)github.com> date: 2018-11-05T20:47:11-08:00 summary: closes bpo-35171: Fix test_TimeRE_recreation_timezone failure on some systems. (GH-10347) The test depended on '/usr/share/zoneinfo/posixrules' or equivalent because it set TZ without explicit DST transition rules. At least on OpenSUSE Tumbleweed that file is linked to '/etc/localtime', making the test fail with certain local timezones, such as 'Europe/Moscow' which doesn't have DST transitions since 2011. (cherry picked from commit f1b9ad3d38c11676b45edcbf2369239bae436e56) Co-authored-by: Alexey Izbyshev <izbyshev(a)ispras.ru> files: M Lib/test/test_strptime.py diff --git a/Lib/test/test_strptime.py b/Lib/test/test_strptime.py index a3358a493e53..623da401eee4 100644 --- a/Lib/test/test_strptime.py +++ b/Lib/test/test_strptime.py @@ -692,7 +692,7 @@ def test_TimeRE_recreation_locale(self): finally: locale.setlocale(locale.LC_TIME, locale_info) - @support.run_with_tz('STD-1DST') + @support.run_with_tz('STD-1DST,M4.1.0,M10.1.0') def test_TimeRE_recreation_timezone(self): # The TimeRE instance should be recreated upon changing the timezone. oldtzname = time.tzname

1 0

closes bpo-35171: Fix test_TimeRE_recreation_timezone failure on some systems. (GH-10347)
by Benjamin Peterson 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/f1b9ad3d38c11676b45edcbf2369239bae… commit: f1b9ad3d38c11676b45edcbf2369239bae436e56 branch: master author: Alexey Izbyshev <izbyshev(a)ispras.ru> committer: Benjamin Peterson <benjamin(a)python.org> date: 2018-11-05T20:29:07-08:00 summary: closes bpo-35171: Fix test_TimeRE_recreation_timezone failure on some systems. (GH-10347) The test depended on '/usr/share/zoneinfo/posixrules' or equivalent because it set TZ without explicit DST transition rules. At least on OpenSUSE Tumbleweed that file is linked to '/etc/localtime', making the test fail with certain local timezones, such as 'Europe/Moscow' which doesn't have DST transitions since 2011. files: M Lib/test/test_strptime.py diff --git a/Lib/test/test_strptime.py b/Lib/test/test_strptime.py index a3358a493e53..623da401eee4 100644 --- a/Lib/test/test_strptime.py +++ b/Lib/test/test_strptime.py @@ -692,7 +692,7 @@ def test_TimeRE_recreation_locale(self): finally: locale.setlocale(locale.LC_TIME, locale_info) - @support.run_with_tz('STD-1DST') + @support.run_with_tz('STD-1DST,M4.1.0,M10.1.0') def test_TimeRE_recreation_timezone(self): # The TimeRE instance should be recreated upon changing the timezone. oldtzname = time.tzname

1 0

bpo-35099: Update idlelib/help.html (GH-10353)
by Miss Islington (bot) 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/54bcb6c0f185be29b2a626d2f1430c110c… commit: 54bcb6c0f185be29b2a626d2f1430c110c823a7d branch: 3.6 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: GitHub <noreply(a)github.com> date: 2018-11-05T19:39:53-08:00 summary: bpo-35099: Update idlelib/help.html (GH-10353) (This should have been done with the first PR for this issue.) (cherry picked from commit f1d3efc2fba704692d539acc3cb0376a1dd9d98f) Co-authored-by: Terry Jan Reedy <tjreedy(a)udel.edu> files: M Lib/idlelib/help.html diff --git a/Lib/idlelib/help.html b/Lib/idlelib/help.html index 24fd77da904e..1cd9b6913de8 100644 --- a/Lib/idlelib/help.html +++ b/Lib/idlelib/help.html @@ -616,23 +616,33 @@ <h3>Startup failure<a class="headerlink" href="#startup-failure" title="Permalin <p>If IDLE quits with no message, and it was not started from a console, try starting from a console (<code class="docutils literal notranslate"><span class="pre">python</span> <span class="pre">-m</span> <span class="pre">idlelib)</span></code> and see if a message appears.</p> </div> -<div class="section" id="idle-console-differences"> -<h3>IDLE-console differences<a class="headerlink" href="#idle-console-differences" title="Permalink to this headline">¶</a></h3> +<div class="section" id="running-user-code"> +<h3>Running user code<a class="headerlink" href="#running-user-code" title="Permalink to this headline">¶</a></h3> <p>With rare exceptions, the result of executing Python code with IDLE is -intended to be the same as executing the same code in a console window. +intended to be the same as executing the same code by the default method, +directly with Python in a text-mode system console or terminal window. However, the different interface and operation occasionally affect -visible results. For instance, <code class="docutils literal notranslate"><span class="pre">sys.modules</span></code> starts with more entries.</p> -<p>IDLE also replaces <code class="docutils literal notranslate"><span class="pre">sys.stdin</span></code>, <code class="docutils literal notranslate"><span class="pre">sys.stdout</span></code>, and <code class="docutils literal notranslate"><span class="pre">sys.stderr</span></code> with -objects that get input from and send output to the Shell window. -When Shell has the focus, it controls the keyboard and screen. This is +visible results. For instance, <code class="docutils literal notranslate"><span class="pre">sys.modules</span></code> starts with more entries, +and <code class="docutils literal notranslate"><span class="pre">threading.activeCount()</span></code> returns 2 instead of 1.</p> +<p>By default, IDLE runs user code in a separate OS process rather than in +the user interface process that runs the shell and editor. In the execution +process, it replaces <code class="docutils literal notranslate"><span class="pre">sys.stdin</span></code>, <code class="docutils literal notranslate"><span class="pre">sys.stdout</span></code>, and <code class="docutils literal notranslate"><span class="pre">sys.stderr</span></code> +with objects that get input from and send output to the Shell window. +The original values stored in <code class="docutils literal notranslate"><span class="pre">sys.__stdin__</span></code>, <code class="docutils literal notranslate"><span class="pre">sys.__stdout__</span></code>, and +<code class="docutils literal notranslate"><span class="pre">sys.__stderr__</span></code> are not touched, but may be <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p> +<p>When Shell 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 notranslate"><span class="pre">sys</span></code> is reset with <code class="docutils literal notranslate"><span class="pre">importlib.reload(sys)</span></code>, -IDLE’s changes are lost and things like <code class="docutils literal notranslate"><span class="pre">input</span></code>, <code class="docutils literal notranslate"><span class="pre">raw_input</span></code>, and -<code class="docutils literal notranslate"><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. IDLE uses -<code class="docutils literal notranslate"><span class="pre">exec</span></code> to run each statement. As a result, <code class="docutils literal notranslate"><span class="pre">'__builtins__'</span></code> is always -defined for each statement.</p> +and screen will not work. These include system-specific functions that +determine whether a key has been pressed and if so, which.</p> +<p>IDLE’s standard stream replacements are not inherited by subprocesses +created in the execution process, whether directly by user code or by modules +such as multiprocessing. If such subprocess use <code class="docutils literal notranslate"><span class="pre">input</span></code> from sys.stdin +or <code class="docutils literal notranslate"><span class="pre">print</span></code> or <code class="docutils literal notranslate"><span class="pre">write</span></code> to sys.stdout or sys.stderr, +IDLE should be started in a command line window. The secondary subprocess +will then be attached to that window for input and output.</p> +<p>If <code class="docutils literal notranslate"><span class="pre">sys</span></code> is reset by user code, such as with <code class="docutils literal notranslate"><span class="pre">importlib.reload(sys)</span></code>, +IDLE’s changes are lost and input from the keyboard and output to the screen +will not work correctly.</p> </div> <div class="section" id="developing-tkinter-applications"> <h3>Developing tkinter applications<a class="headerlink" href="#developing-tkinter-applications" title="Permalink to this headline">¶</a></h3> @@ -752,7 +762,7 @@ <h3><a href="../contents.html">Table of Contents</a></h3> <li><a class="reference internal" href="#startup-and-code-execution">Startup and code execution</a><ul> <li><a class="reference internal" href="#command-line-usage">Command line usage</a></li> <li><a class="reference internal" href="#startup-failure">Startup failure</a></li> -<li><a class="reference internal" href="#idle-console-differences">IDLE-console differences</a></li> +<li><a class="reference internal" href="#running-user-code">Running user code</a></li> <li><a class="reference internal" href="#developing-tkinter-applications">Developing tkinter applications</a></li> <li><a class="reference internal" href="#running-without-a-subprocess">Running without a subprocess</a></li> </ul> @@ -841,7 +851,7 @@ <h3>Navigation</h3> <br /> <br /> - Last updated on Oct 28, 2018. + Last updated on Nov 05, 2018. <a href="https://docs.python.org/3/bugs.html">Found a bug</a>? <br />

1 0

bpo-35099: Update idlelib/help.html (GH-10353)
by Miss Islington (bot) 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/4a46295a95bc2e7a93bcf0ce4cdaeeeb48… commit: 4a46295a95bc2e7a93bcf0ce4cdaeeeb48729069 branch: 3.7 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: GitHub <noreply(a)github.com> date: 2018-11-05T19:36:12-08:00 summary: bpo-35099: Update idlelib/help.html (GH-10353) (This should have been done with the first PR for this issue.) (cherry picked from commit f1d3efc2fba704692d539acc3cb0376a1dd9d98f) Co-authored-by: Terry Jan Reedy <tjreedy(a)udel.edu> files: M Lib/idlelib/help.html diff --git a/Lib/idlelib/help.html b/Lib/idlelib/help.html index 24fd77da904e..1cd9b6913de8 100644 --- a/Lib/idlelib/help.html +++ b/Lib/idlelib/help.html @@ -616,23 +616,33 @@ <h3>Startup failure<a class="headerlink" href="#startup-failure" title="Permalin <p>If IDLE quits with no message, and it was not started from a console, try starting from a console (<code class="docutils literal notranslate"><span class="pre">python</span> <span class="pre">-m</span> <span class="pre">idlelib)</span></code> and see if a message appears.</p> </div> -<div class="section" id="idle-console-differences"> -<h3>IDLE-console differences<a class="headerlink" href="#idle-console-differences" title="Permalink to this headline">¶</a></h3> +<div class="section" id="running-user-code"> +<h3>Running user code<a class="headerlink" href="#running-user-code" title="Permalink to this headline">¶</a></h3> <p>With rare exceptions, the result of executing Python code with IDLE is -intended to be the same as executing the same code in a console window. +intended to be the same as executing the same code by the default method, +directly with Python in a text-mode system console or terminal window. However, the different interface and operation occasionally affect -visible results. For instance, <code class="docutils literal notranslate"><span class="pre">sys.modules</span></code> starts with more entries.</p> -<p>IDLE also replaces <code class="docutils literal notranslate"><span class="pre">sys.stdin</span></code>, <code class="docutils literal notranslate"><span class="pre">sys.stdout</span></code>, and <code class="docutils literal notranslate"><span class="pre">sys.stderr</span></code> with -objects that get input from and send output to the Shell window. -When Shell has the focus, it controls the keyboard and screen. This is +visible results. For instance, <code class="docutils literal notranslate"><span class="pre">sys.modules</span></code> starts with more entries, +and <code class="docutils literal notranslate"><span class="pre">threading.activeCount()</span></code> returns 2 instead of 1.</p> +<p>By default, IDLE runs user code in a separate OS process rather than in +the user interface process that runs the shell and editor. In the execution +process, it replaces <code class="docutils literal notranslate"><span class="pre">sys.stdin</span></code>, <code class="docutils literal notranslate"><span class="pre">sys.stdout</span></code>, and <code class="docutils literal notranslate"><span class="pre">sys.stderr</span></code> +with objects that get input from and send output to the Shell window. +The original values stored in <code class="docutils literal notranslate"><span class="pre">sys.__stdin__</span></code>, <code class="docutils literal notranslate"><span class="pre">sys.__stdout__</span></code>, and +<code class="docutils literal notranslate"><span class="pre">sys.__stderr__</span></code> are not touched, but may be <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p> +<p>When Shell 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 notranslate"><span class="pre">sys</span></code> is reset with <code class="docutils literal notranslate"><span class="pre">importlib.reload(sys)</span></code>, -IDLE’s changes are lost and things like <code class="docutils literal notranslate"><span class="pre">input</span></code>, <code class="docutils literal notranslate"><span class="pre">raw_input</span></code>, and -<code class="docutils literal notranslate"><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. IDLE uses -<code class="docutils literal notranslate"><span class="pre">exec</span></code> to run each statement. As a result, <code class="docutils literal notranslate"><span class="pre">'__builtins__'</span></code> is always -defined for each statement.</p> +and screen will not work. These include system-specific functions that +determine whether a key has been pressed and if so, which.</p> +<p>IDLE’s standard stream replacements are not inherited by subprocesses +created in the execution process, whether directly by user code or by modules +such as multiprocessing. If such subprocess use <code class="docutils literal notranslate"><span class="pre">input</span></code> from sys.stdin +or <code class="docutils literal notranslate"><span class="pre">print</span></code> or <code class="docutils literal notranslate"><span class="pre">write</span></code> to sys.stdout or sys.stderr, +IDLE should be started in a command line window. The secondary subprocess +will then be attached to that window for input and output.</p> +<p>If <code class="docutils literal notranslate"><span class="pre">sys</span></code> is reset by user code, such as with <code class="docutils literal notranslate"><span class="pre">importlib.reload(sys)</span></code>, +IDLE’s changes are lost and input from the keyboard and output to the screen +will not work correctly.</p> </div> <div class="section" id="developing-tkinter-applications"> <h3>Developing tkinter applications<a class="headerlink" href="#developing-tkinter-applications" title="Permalink to this headline">¶</a></h3> @@ -752,7 +762,7 @@ <h3><a href="../contents.html">Table of Contents</a></h3> <li><a class="reference internal" href="#startup-and-code-execution">Startup and code execution</a><ul> <li><a class="reference internal" href="#command-line-usage">Command line usage</a></li> <li><a class="reference internal" href="#startup-failure">Startup failure</a></li> -<li><a class="reference internal" href="#idle-console-differences">IDLE-console differences</a></li> +<li><a class="reference internal" href="#running-user-code">Running user code</a></li> <li><a class="reference internal" href="#developing-tkinter-applications">Developing tkinter applications</a></li> <li><a class="reference internal" href="#running-without-a-subprocess">Running without a subprocess</a></li> </ul> @@ -841,7 +851,7 @@ <h3>Navigation</h3> <br /> <br /> - Last updated on Oct 28, 2018. + Last updated on Nov 05, 2018. <a href="https://docs.python.org/3/bugs.html">Found a bug</a>? <br />

1 0

bpo-35099: Update idlelib/help.html (#10353)
by Terry Jan Reedy 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/f1d3efc2fba704692d539acc3cb0376a1d… commit: f1d3efc2fba704692d539acc3cb0376a1dd9d98f branch: master author: Terry Jan Reedy <tjreedy(a)udel.edu> committer: GitHub <noreply(a)github.com> date: 2018-11-05T22:17:57-05:00 summary: bpo-35099: Update idlelib/help.html (#10353) (This should have been done with the first PR for this issue.) files: M Lib/idlelib/help.html diff --git a/Lib/idlelib/help.html b/Lib/idlelib/help.html index 24fd77da904e..1cd9b6913de8 100644 --- a/Lib/idlelib/help.html +++ b/Lib/idlelib/help.html @@ -616,23 +616,33 @@ <h3>Startup failure<a class="headerlink" href="#startup-failure" title="Permalin <p>If IDLE quits with no message, and it was not started from a console, try starting from a console (<code class="docutils literal notranslate"><span class="pre">python</span> <span class="pre">-m</span> <span class="pre">idlelib)</span></code> and see if a message appears.</p> </div> -<div class="section" id="idle-console-differences"> -<h3>IDLE-console differences<a class="headerlink" href="#idle-console-differences" title="Permalink to this headline">¶</a></h3> +<div class="section" id="running-user-code"> +<h3>Running user code<a class="headerlink" href="#running-user-code" title="Permalink to this headline">¶</a></h3> <p>With rare exceptions, the result of executing Python code with IDLE is -intended to be the same as executing the same code in a console window. +intended to be the same as executing the same code by the default method, +directly with Python in a text-mode system console or terminal window. However, the different interface and operation occasionally affect -visible results. For instance, <code class="docutils literal notranslate"><span class="pre">sys.modules</span></code> starts with more entries.</p> -<p>IDLE also replaces <code class="docutils literal notranslate"><span class="pre">sys.stdin</span></code>, <code class="docutils literal notranslate"><span class="pre">sys.stdout</span></code>, and <code class="docutils literal notranslate"><span class="pre">sys.stderr</span></code> with -objects that get input from and send output to the Shell window. -When Shell has the focus, it controls the keyboard and screen. This is +visible results. For instance, <code class="docutils literal notranslate"><span class="pre">sys.modules</span></code> starts with more entries, +and <code class="docutils literal notranslate"><span class="pre">threading.activeCount()</span></code> returns 2 instead of 1.</p> +<p>By default, IDLE runs user code in a separate OS process rather than in +the user interface process that runs the shell and editor. In the execution +process, it replaces <code class="docutils literal notranslate"><span class="pre">sys.stdin</span></code>, <code class="docutils literal notranslate"><span class="pre">sys.stdout</span></code>, and <code class="docutils literal notranslate"><span class="pre">sys.stderr</span></code> +with objects that get input from and send output to the Shell window. +The original values stored in <code class="docutils literal notranslate"><span class="pre">sys.__stdin__</span></code>, <code class="docutils literal notranslate"><span class="pre">sys.__stdout__</span></code>, and +<code class="docutils literal notranslate"><span class="pre">sys.__stderr__</span></code> are not touched, but may be <code class="docutils literal notranslate"><span class="pre">None</span></code>.</p> +<p>When Shell 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 notranslate"><span class="pre">sys</span></code> is reset with <code class="docutils literal notranslate"><span class="pre">importlib.reload(sys)</span></code>, -IDLE’s changes are lost and things like <code class="docutils literal notranslate"><span class="pre">input</span></code>, <code class="docutils literal notranslate"><span class="pre">raw_input</span></code>, and -<code class="docutils literal notranslate"><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. IDLE uses -<code class="docutils literal notranslate"><span class="pre">exec</span></code> to run each statement. As a result, <code class="docutils literal notranslate"><span class="pre">'__builtins__'</span></code> is always -defined for each statement.</p> +and screen will not work. These include system-specific functions that +determine whether a key has been pressed and if so, which.</p> +<p>IDLE’s standard stream replacements are not inherited by subprocesses +created in the execution process, whether directly by user code or by modules +such as multiprocessing. If such subprocess use <code class="docutils literal notranslate"><span class="pre">input</span></code> from sys.stdin +or <code class="docutils literal notranslate"><span class="pre">print</span></code> or <code class="docutils literal notranslate"><span class="pre">write</span></code> to sys.stdout or sys.stderr, +IDLE should be started in a command line window. The secondary subprocess +will then be attached to that window for input and output.</p> +<p>If <code class="docutils literal notranslate"><span class="pre">sys</span></code> is reset by user code, such as with <code class="docutils literal notranslate"><span class="pre">importlib.reload(sys)</span></code>, +IDLE’s changes are lost and input from the keyboard and output to the screen +will not work correctly.</p> </div> <div class="section" id="developing-tkinter-applications"> <h3>Developing tkinter applications<a class="headerlink" href="#developing-tkinter-applications" title="Permalink to this headline">¶</a></h3> @@ -752,7 +762,7 @@ <h3><a href="../contents.html">Table of Contents</a></h3> <li><a class="reference internal" href="#startup-and-code-execution">Startup and code execution</a><ul> <li><a class="reference internal" href="#command-line-usage">Command line usage</a></li> <li><a class="reference internal" href="#startup-failure">Startup failure</a></li> -<li><a class="reference internal" href="#idle-console-differences">IDLE-console differences</a></li> +<li><a class="reference internal" href="#running-user-code">Running user code</a></li> <li><a class="reference internal" href="#developing-tkinter-applications">Developing tkinter applications</a></li> <li><a class="reference internal" href="#running-without-a-subprocess">Running without a subprocess</a></li> </ul> @@ -841,7 +851,7 @@ <h3>Navigation</h3> <br /> <br /> - Last updated on Oct 28, 2018. + Last updated on Nov 05, 2018. <a href="https://docs.python.org/3/bugs.html">Found a bug</a>? <br />

1 0

bpo-35099: Improve the doc about IDLE running user code. (GH-10350)
by Miss Islington (bot) 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/927a113ae2be33a9dd929569930f28948a… commit: 927a113ae2be33a9dd929569930f28948aa5c965 branch: 3.6 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: GitHub <noreply(a)github.com> date: 2018-11-05T18:35:51-08:00 summary: bpo-35099: Improve the doc about IDLE running user code. (GH-10350) The section is renamed from "IDLE -- console differences". It mostly covers the implications of using custom sys.stdxxx objects. (cherry picked from commit 5e7909032491cef17754a3208872655fe350e9be) Co-authored-by: Terry Jan Reedy <tjreedy(a)udel.edu> files: A Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst M Doc/library/idle.rst diff --git a/Doc/library/idle.rst b/Doc/library/idle.rst index 0826d99b6336..a4432190bbb0 100644 --- a/Doc/library/idle.rst +++ b/Doc/library/idle.rst @@ -563,7 +563,6 @@ looked for in the user's home directory. Statements in this file will be executed in the Tk namespace, so this file is not useful for importing functions to be used from IDLE's Python shell. - Command line usage ^^^^^^^^^^^^^^^^^^ @@ -591,7 +590,6 @@ If there are arguments: * Otherwise, arguments are files opened for editing and ``sys.argv`` reflects the arguments passed to IDLE itself. - Startup failure ^^^^^^^^^^^^^^^ @@ -635,27 +633,38 @@ be to delete one or more of the configuration files. If IDLE quits with no message, and it was not started from a console, try starting from a console (``python -m idlelib)`` and see if a message appears. - -IDLE-console differences -^^^^^^^^^^^^^^^^^^^^^^^^ +Running user code +^^^^^^^^^^^^^^^^^ With rare exceptions, the result of executing Python code with IDLE is -intended to be the same as executing the same code in a console window. +intended to be the same as executing the same code by the default method, +directly with Python in a text-mode system console or terminal window. However, the different interface and operation occasionally affect -visible results. For instance, ``sys.modules`` starts with more entries. +visible results. For instance, ``sys.modules`` starts with more entries, +and ``threading.activeCount()`` returns 2 instead of 1. + +By default, IDLE runs user code in a separate OS process rather than in +the user interface process that runs the shell and editor. In the execution +process, it replaces ``sys.stdin``, ``sys.stdout``, and ``sys.stderr`` +with objects that get input from and send output to the Shell window. +The original values stored in ``sys.__stdin__``, ``sys.__stdout__``, and +``sys.__stderr__`` are not touched, but may be ``None``. -IDLE also replaces ``sys.stdin``, ``sys.stdout``, and ``sys.stderr`` with -objects that get input from and send output to the Shell window. When Shell 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 like ``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. IDLE uses -``exec`` to run each statement. As a result, ``'__builtins__'`` is always -defined for each statement. +and screen will not work. These include system-specific functions that +determine whether a key has been pressed and if so, which. + +IDLE's standard stream replacements are not inherited by subprocesses +created in the execution process, whether directly by user code or by modules +such as multiprocessing. If such subprocess use ``input`` from sys.stdin +or ``print`` or ``write`` to sys.stdout or sys.stderr, +IDLE should be started in a command line window. The secondary subprocess +will then be attached to that window for input and output. + +If ``sys`` is reset by user code, such as with ``importlib.reload(sys)``, +IDLE's changes are lost and input from the keyboard and output to the screen +will not work correctly. Developing tkinter applications ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst b/Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst new file mode 100644 index 000000000000..1459f20cb78f --- /dev/null +++ b/Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst @@ -0,0 +1,3 @@ +Improve the doc about IDLE running user code. The section is renamed from +"IDLE -- console differences" is renamed "Running user code". +It mostly covers the implications of using custom sys.stdxxx objects.

1 0

bpo-35099: Improve the doc about IDLE running user code. (GH-10350)
by Miss Islington (bot) 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/a437c285fa4f21720802e7a91770b2281d… commit: a437c285fa4f21720802e7a91770b2281d576554 branch: 3.7 author: Miss Islington (bot) <31488909+miss-islington(a)users.noreply.github.com> committer: GitHub <noreply(a)github.com> date: 2018-11-05T18:35:18-08:00 summary: bpo-35099: Improve the doc about IDLE running user code. (GH-10350) The section is renamed from "IDLE -- console differences". It mostly covers the implications of using custom sys.stdxxx objects. (cherry picked from commit 5e7909032491cef17754a3208872655fe350e9be) Co-authored-by: Terry Jan Reedy <tjreedy(a)udel.edu> files: A Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst M Doc/library/idle.rst diff --git a/Doc/library/idle.rst b/Doc/library/idle.rst index 645bd612618b..c5015bf30cfb 100644 --- a/Doc/library/idle.rst +++ b/Doc/library/idle.rst @@ -563,7 +563,6 @@ looked for in the user's home directory. Statements in this file will be executed in the Tk namespace, so this file is not useful for importing functions to be used from IDLE's Python shell. - Command line usage ^^^^^^^^^^^^^^^^^^ @@ -591,7 +590,6 @@ If there are arguments: * Otherwise, arguments are files opened for editing and ``sys.argv`` reflects the arguments passed to IDLE itself. - Startup failure ^^^^^^^^^^^^^^^ @@ -635,27 +633,38 @@ be to delete one or more of the configuration files. If IDLE quits with no message, and it was not started from a console, try starting from a console (``python -m idlelib)`` and see if a message appears. - -IDLE-console differences -^^^^^^^^^^^^^^^^^^^^^^^^ +Running user code +^^^^^^^^^^^^^^^^^ With rare exceptions, the result of executing Python code with IDLE is -intended to be the same as executing the same code in a console window. +intended to be the same as executing the same code by the default method, +directly with Python in a text-mode system console or terminal window. However, the different interface and operation occasionally affect -visible results. For instance, ``sys.modules`` starts with more entries. +visible results. For instance, ``sys.modules`` starts with more entries, +and ``threading.activeCount()`` returns 2 instead of 1. + +By default, IDLE runs user code in a separate OS process rather than in +the user interface process that runs the shell and editor. In the execution +process, it replaces ``sys.stdin``, ``sys.stdout``, and ``sys.stderr`` +with objects that get input from and send output to the Shell window. +The original values stored in ``sys.__stdin__``, ``sys.__stdout__``, and +``sys.__stderr__`` are not touched, but may be ``None``. -IDLE also replaces ``sys.stdin``, ``sys.stdout``, and ``sys.stderr`` with -objects that get input from and send output to the Shell window. When Shell 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 like ``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. IDLE uses -``exec`` to run each statement. As a result, ``'__builtins__'`` is always -defined for each statement. +and screen will not work. These include system-specific functions that +determine whether a key has been pressed and if so, which. + +IDLE's standard stream replacements are not inherited by subprocesses +created in the execution process, whether directly by user code or by modules +such as multiprocessing. If such subprocess use ``input`` from sys.stdin +or ``print`` or ``write`` to sys.stdout or sys.stderr, +IDLE should be started in a command line window. The secondary subprocess +will then be attached to that window for input and output. + +If ``sys`` is reset by user code, such as with ``importlib.reload(sys)``, +IDLE's changes are lost and input from the keyboard and output to the screen +will not work correctly. Developing tkinter applications ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst b/Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst new file mode 100644 index 000000000000..1459f20cb78f --- /dev/null +++ b/Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst @@ -0,0 +1,3 @@ +Improve the doc about IDLE running user code. The section is renamed from +"IDLE -- console differences" is renamed "Running user code". +It mostly covers the implications of using custom sys.stdxxx objects.

1 0

bpo-35099: Improve the doc about IDLE running user code. (#10350)
by Terry Jan Reedy 05 Nov '18

05 Nov '18

https://github.com/python/cpython/commit/5e7909032491cef17754a3208872655fe3… commit: 5e7909032491cef17754a3208872655fe350e9be branch: master author: Terry Jan Reedy <tjreedy(a)udel.edu> committer: GitHub <noreply(a)github.com> date: 2018-11-05T21:30:32-05:00 summary: bpo-35099: Improve the doc about IDLE running user code. (#10350) The section is renamed from "IDLE -- console differences". It mostly covers the implications of using custom sys.stdxxx objects. files: A Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst M Doc/library/idle.rst diff --git a/Doc/library/idle.rst b/Doc/library/idle.rst index 645bd612618b..c5015bf30cfb 100644 --- a/Doc/library/idle.rst +++ b/Doc/library/idle.rst @@ -563,7 +563,6 @@ looked for in the user's home directory. Statements in this file will be executed in the Tk namespace, so this file is not useful for importing functions to be used from IDLE's Python shell. - Command line usage ^^^^^^^^^^^^^^^^^^ @@ -591,7 +590,6 @@ If there are arguments: * Otherwise, arguments are files opened for editing and ``sys.argv`` reflects the arguments passed to IDLE itself. - Startup failure ^^^^^^^^^^^^^^^ @@ -635,27 +633,38 @@ be to delete one or more of the configuration files. If IDLE quits with no message, and it was not started from a console, try starting from a console (``python -m idlelib)`` and see if a message appears. - -IDLE-console differences -^^^^^^^^^^^^^^^^^^^^^^^^ +Running user code +^^^^^^^^^^^^^^^^^ With rare exceptions, the result of executing Python code with IDLE is -intended to be the same as executing the same code in a console window. +intended to be the same as executing the same code by the default method, +directly with Python in a text-mode system console or terminal window. However, the different interface and operation occasionally affect -visible results. For instance, ``sys.modules`` starts with more entries. +visible results. For instance, ``sys.modules`` starts with more entries, +and ``threading.activeCount()`` returns 2 instead of 1. + +By default, IDLE runs user code in a separate OS process rather than in +the user interface process that runs the shell and editor. In the execution +process, it replaces ``sys.stdin``, ``sys.stdout``, and ``sys.stderr`` +with objects that get input from and send output to the Shell window. +The original values stored in ``sys.__stdin__``, ``sys.__stdout__``, and +``sys.__stderr__`` are not touched, but may be ``None``. -IDLE also replaces ``sys.stdin``, ``sys.stdout``, and ``sys.stderr`` with -objects that get input from and send output to the Shell window. When Shell 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 like ``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. IDLE uses -``exec`` to run each statement. As a result, ``'__builtins__'`` is always -defined for each statement. +and screen will not work. These include system-specific functions that +determine whether a key has been pressed and if so, which. + +IDLE's standard stream replacements are not inherited by subprocesses +created in the execution process, whether directly by user code or by modules +such as multiprocessing. If such subprocess use ``input`` from sys.stdin +or ``print`` or ``write`` to sys.stdout or sys.stderr, +IDLE should be started in a command line window. The secondary subprocess +will then be attached to that window for input and output. + +If ``sys`` is reset by user code, such as with ``importlib.reload(sys)``, +IDLE's changes are lost and input from the keyboard and output to the screen +will not work correctly. Developing tkinter applications ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst b/Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst new file mode 100644 index 000000000000..1459f20cb78f --- /dev/null +++ b/Misc/NEWS.d/next/IDLE/2018-11-05-20-43-08.bpo-35099.SVOZXC.rst @@ -0,0 +1,3 @@ +Improve the doc about IDLE running user code. The section is renamed from +"IDLE -- console differences" is renamed "Running user code". +It mostly covers the implications of using custom sys.stdxxx objects.

1 0