<p>IDLE is Python’s Integrated Development and Learning Environment.</p>
<p>IDLE is Python’s Integrated Development and Learning Environment.</p>
<p>IDLE has the following features:</p>
<ulclass="simple">
<li>coded in 100% pure Python, using the <aclass="reference internal"href="tkinter.html#module-tkinter"title="tkinter: Interface to Tcl/Tk for graphical user interfaces"><codeclass="xref py py-mod docutils literal"><spanclass="pre">tkinter</span></code></a> GUI toolkit</li>
<li>coded in 100% pure Python, using the <aclass="reference internal"href="tkinter.html#module-tkinter"title="tkinter: Interface to Tcl/Tk for graphical user interfaces"><codeclass="xref py py-mod docutils literal notranslate"><spanclass="pre">tkinter</span></code></a> GUI toolkit</li>
<li>cross-platform: works mostly the same on Windows, Unix, and Mac OS X</li>
<li>Python shell window (interactive interpreter) with colorizing
of code input, output, and error messages</li>
...
...
@@ -111,24 +107,24 @@ of global and local namespaces</li>
<li>configuration, browsers, and other dialogs</li>
</ul>
<divclass="section"id="menus">
<h2>25.5.1. Menus<aclass="headerlink"href="#menus"title="Permalink to this headline">¶</a></h2>
<h2>26.5.1. Menus<aclass="headerlink"href="#menus"title="Permalink to this headline">¶</a></h2>
<p>IDLE has two main window types, the Shell window and the Editor window. It is
possible to have multiple editor windows simultaneously. Output windows, such
as used for Edit / Find in Files, are a subtype of edit window. They currently
have the same top menu as Editor windows but a different default title and
context menu.</p>
<p>IDLE’s menus dynamically change based on which window is currently selected.
<p>IDLE’s menus dynamically change based on which window is currently selected.
Each menu documented below indicates which window type it is associated with.</p>
<spanid="index-2"></span><h3>25.5.1.4. Run menu (Editor window only)<aclass="headerlink"href="#run-menu-editor-window-only"title="Permalink to this headline">¶</a></h3>
<spanid="index-2"></span><h3>26.5.1.4. Run menu (Editor window only)<aclass="headerlink"href="#run-menu-editor-window-only"title="Permalink to this headline">¶</a></h3>
<dlclass="docutils">
<dt>Python Shell</dt>
<dd>Open or wake up the Python Shell window.</dd>
...
...
@@ -246,15 +242,15 @@ Editor window.</dd>
<dt>Run Module</dt>
<dd>Do Check Module (above). If no error, restart the shell to clean the
environment, then execute the module. Output is displayed in the Shell
window. Note that output requires use of <codeclass="docutils literal"><spanclass="pre">print</span></code> or <codeclass="docutils literal"><spanclass="pre">write</span></code>.
window. Note that output requires use of <codeclass="docutils literal notranslate"><spanclass="pre">print</span></code> or <codeclass="docutils literal notranslate"><spanclass="pre">write</span></code>.
When execution is complete, the Shell retains focus and displays a prompt.
At this point, one may interactively explore the result of execution.
This is similar to executing a file with <codeclass="docutils literal"><spanclass="pre">python</span><spanclass="pre">-i</span><spanclass="pre">file</span></code> at a command
This is similar to executing a file with <codeclass="docutils literal notranslate"><spanclass="pre">python</span><spanclass="pre">-i</span><spanclass="pre">file</span></code> at a command
<h3>25.5.1.9. Help menu (Shell and Editor)<aclass="headerlink"href="#help-menu-shell-and-editor"title="Permalink to this headline">¶</a></h3>
<h3>26.5.1.9. Help menu (Shell and Editor)<aclass="headerlink"href="#help-menu-shell-and-editor"title="Permalink to this headline">¶</a></h3>
<dlclass="docutils">
<dt>About IDLE</dt>
<dd>Display version, copyright, license, credits, and more.</dd>
...
...
@@ -334,7 +331,7 @@ and open docs.python.org showing the latest Python documentation.</dd>
the General tab.</p>
</div>
<divclass="section"id="context-menus">
<spanid="index-4"></span><h3>25.5.1.10. Context Menus<aclass="headerlink"href="#context-menus"title="Permalink to this headline">¶</a></h3>
<spanid="index-4"></span><h3>26.5.1.10. Context Menus<aclass="headerlink"href="#context-menus"title="Permalink to this headline">¶</a></h3>
<p>Open a context menu by right-clicking in a window (Control-click on OS X).
Context menus have the standard clipboard functions also on the Edit menu.</p>
<dlclass="docutils">
...
...
@@ -347,7 +344,7 @@ Context menus have the standard clipboard functions also on the Edit menu.</p>
</dl>
<p>Editor windows also have breakpoint functions. Lines with a breakpoint set are
specially marked. Breakpoints only have an effect when running under the
debugger. Breakpoints for a file are saved in the user’s .idlerc directory.</p>
debugger. Breakpoints for a file are saved in the user’s .idlerc directory.</p>
<dlclass="docutils">
<dt>Set Breakpoint</dt>
<dd>Set a breakpoint on the current line.</dd>
...
...
@@ -362,93 +359,93 @@ debugger. Breakpoints for a file are saved in the user’s .idlerc director
</div>
</div>
<divclass="section"id="editing-and-navigation">
<h2>25.5.2. Editing and navigation<aclass="headerlink"href="#editing-and-navigation"title="Permalink to this headline">¶</a></h2>
<p>In this section, ‘C’ refers to the <codeclass="kbd docutils literal"><spanclass="pre">Control</span></code> key on Windows and Unix and
the <codeclass="kbd docutils literal"><spanclass="pre">Command</span></code> key on Mac OSX.</p>
<h2>26.5.2. Editing and navigation<aclass="headerlink"href="#editing-and-navigation"title="Permalink to this headline">¶</a></h2>
<p>In this section, ‘C’ refers to the <kbdclass="kbd docutils literal notranslate">Control</kbd> key on Windows and Unix and
the <kbdclass="kbd docutils literal notranslate">Command</kbd> key on Mac OSX.</p>
<ul>
<li><pclass="first"><codeclass="kbd docutils literal"><spanclass="pre">Backspace</span></code> deletes to the left; <codeclass="kbd docutils literal"><spanclass="pre">Del</span></code> deletes to the right</p>
<li><pclass="first"><kbdclass="kbd docutils literal notranslate">Backspace</kbd> deletes to the left; <kbdclass="kbd docutils literal notranslate">Del</kbd> deletes to the right</p>
</li>
<li><pclass="first"><codeclass="kbd docutils literal"><spanclass="pre">C-Backspace</span></code> delete word left; <codeclass="kbd docutils literal"><spanclass="pre">C-Del</span></code> delete word to the right</p>
<li><pclass="first"><kbdclass="kbd docutils literal notranslate">C-Backspace</kbd> delete word left; <kbdclass="kbd docutils literal notranslate">C-Del</kbd> delete word to the right</p>
</li>
<li><pclass="first">Arrow keys and <codeclass="kbd docutils literal"><spanclass="pre">Page</span><spanclass="pre">Up</span></code>/<codeclass="kbd docutils literal"><spanclass="pre">Page</span><spanclass="pre">Down</span></code> to move around</p>
<li><pclass="first">Arrow keys and <kbdclass="kbd docutils literal notranslate">Page Up</kbd>/<kbdclass="kbd docutils literal notranslate">Page Down</kbd> to move around</p>
</li>
<li><pclass="first"><codeclass="kbd docutils literal"><spanclass="pre">C-LeftArrow</span></code> and <codeclass="kbd docutils literal"><spanclass="pre">C-RightArrow</span></code> moves by words</p>
<li><pclass="first"><kbdclass="kbd docutils literal notranslate">C-LeftArrow</kbd> and <kbdclass="kbd docutils literal notranslate">C-RightArrow</kbd> moves by words</p>
</li>
<li><pclass="first"><codeclass="kbd docutils literal"><spanclass="pre">Home</span></code>/<codeclass="kbd docutils literal"><spanclass="pre">End</span></code> go to begin/end of line</p>
<li><pclass="first"><kbdclass="kbd docutils literal notranslate">Home</kbd>/<kbdclass="kbd docutils literal notranslate">End</kbd> go to begin/end of line</p>
</li>
<li><pclass="first"><codeclass="kbd docutils literal"><spanclass="pre">C-Home</span></code>/<codeclass="kbd docutils literal"><spanclass="pre">C-End</span></code> go to begin/end of file</p>
<li><pclass="first"><kbdclass="kbd docutils literal notranslate">C-Home</kbd>/<kbdclass="kbd docutils literal notranslate">C-End</kbd> go to begin/end of file</p>
</li>
<li><pclass="first">Some useful Emacs bindings are inherited from Tcl/Tk:</p>
<blockquote>
<div><ulclass="simple">
<li><codeclass="kbd docutils literal"><spanclass="pre">C-a</span></code> beginning of line</li>
<li><codeclass="kbd docutils literal"><spanclass="pre">C-e</span></code> end of line</li>
<li><codeclass="kbd docutils literal"><spanclass="pre">C-k</span></code> kill line (but doesn’t put it in clipboard)</li>
<li><codeclass="kbd docutils literal"><spanclass="pre">C-l</span></code> center window around the insertion point</li>
<li><codeclass="kbd docutils literal"><spanclass="pre">C-b</span></code> go backward one character without deleting (usually you can
<li><kbdclass="kbd docutils literal notranslate">C-a</kbd> beginning of line</li>
<li><kbdclass="kbd docutils literal notranslate">C-e</kbd> end of line</li>
<li><kbdclass="kbd docutils literal notranslate">C-k</kbd> kill line (but doesn’t put it in clipboard)</li>
<li><kbdclass="kbd docutils literal notranslate">C-l</kbd> center window around the insertion point</li>
<li><kbdclass="kbd docutils literal notranslate">C-b</kbd> go backward one character without deleting (usually you can
also use the cursor key for this)</li>
<li><codeclass="kbd docutils literal"><spanclass="pre">C-f</span></code> go forward one character without deleting (usually you can
<li><kbdclass="kbd docutils literal notranslate">C-f</kbd> go forward one character without deleting (usually you can
also use the cursor key for this)</li>
<li><codeclass="kbd docutils literal"><spanclass="pre">C-p</span></code> go up one line (usually you can also use the cursor key for
<li><kbdclass="kbd docutils literal notranslate">C-p</kbd> go up one line (usually you can also use the cursor key for
this)</li>
<li><codeclass="kbd docutils literal"><spanclass="pre">C-d</span></code> delete next character</li>
<li><kbdclass="kbd docutils literal notranslate">C-d</kbd> delete next character</li>
</ul>
</div></blockquote>
</li>
</ul>
<p>Standard keybindings (like <codeclass="kbd docutils literal"><spanclass="pre">C-c</span></code> to copy and <codeclass="kbd docutils literal"><spanclass="pre">C-v</span></code> to paste)
<p>Standard keybindings (like <kbdclass="kbd docutils literal notranslate">C-c</kbd> to copy and <kbdclass="kbd docutils literal notranslate">C-v</kbd> to paste)
may work. Keybindings are selected in the Configure IDLE dialog.</p>
<divclass="section"id="automatic-indentation">
<h3>25.5.2.1. Automatic indentation<aclass="headerlink"href="#automatic-indentation"title="Permalink to this headline">¶</a></h3>
<h3>26.5.2.1. Automatic indentation<aclass="headerlink"href="#automatic-indentation"title="Permalink to this headline">¶</a></h3>
<p>After a block-opening statement, the next line is indented by 4 spaces (in the
Python Shell window by one tab). After certain keywords (break, return etc.)
the next line is dedented. In leading indentation, <codeclass="kbd docutils literal"><spanclass="pre">Backspace</span></code> deletes up
to 4 spaces if they are there. <codeclass="kbd docutils literal"><spanclass="pre">Tab</span></code> inserts spaces (in the Python
the next line is dedented. In leading indentation, <kbdclass="kbd docutils literal notranslate">Backspace</kbd> deletes up
to 4 spaces if they are there. <kbdclass="kbd docutils literal notranslate">Tab</kbd> inserts spaces (in the Python
Shell window one tab), number depends on Indent width. Currently, tabs
are restricted to four spaces due to Tcl/Tk limitations.</p>
<p>See also the indent/dedent region commands in the edit menu.</p>
</div>
<divclass="section"id="completions">
<h3>25.5.2.2. Completions<aclass="headerlink"href="#completions"title="Permalink to this headline">¶</a></h3>
<h3>26.5.2.2. Completions<aclass="headerlink"href="#completions"title="Permalink to this headline">¶</a></h3>
<p>Completions are supplied for functions, classes, and attributes of classes,
both built-in and user-defined. Completions are also provided for
filenames.</p>
<p>The AutoCompleteWindow (ACW) will open after a predefined delay (default is
two seconds) after a ‘.’ or (in a string) an os.sep is typed. If after one
two seconds) after a ‘.’ or (in a string) an os.sep is typed. If after one
of those characters (plus zero or more other characters) a tab is typed
the ACW will open immediately if a possible continuation is found.</p>
<p>If there is only one possible completion for the characters entered, a
<codeclass="kbd docutils literal"><spanclass="pre">Tab</span></code> will supply that completion without opening the ACW.</p>
<p>‘Show Completions’ will force open a completions window, by default the
<codeclass="kbd docutils literal"><spanclass="pre">C-space</span></code> will open a completions window. In an empty
<kbdclass="kbd docutils literal notranslate">Tab</kbd> will supply that completion without opening the ACW.</p>
<p>‘Show Completions’ will force open a completions window, by default the
<kbdclass="kbd docutils literal notranslate">C-space</kbd> will open a completions window. In an empty
string, this will contain the files in the current directory. On a
blank line, it will contain the built-in and user-defined functions and
classes in the current namespaces, plus any modules imported. If some
characters have been entered, the ACW will attempt to be more specific.</p>
<p>If a string of characters is typed, the ACW selection will jump to the
entry most closely matching those characters. Entering a <codeclass="kbd docutils literal"><spanclass="pre">tab</span></code> will
entry most closely matching those characters. Entering a <kbdclass="kbd docutils literal notranslate">tab</kbd> will
cause the longest non-ambiguous match to be entered in the Editor window or
Shell. Two <codeclass="kbd docutils literal"><spanclass="pre">tab</span></code> in a row will supply the current ACW selection, as
Shell. Two <kbdclass="kbd docutils literal notranslate">tab</kbd> in a row will supply the current ACW selection, as
will return or a double click. Cursor keys, Page Up/Down, mouse selection,
and the scroll wheel all operate on the ACW.</p>
<p>“Hidden” attributes can be accessed by typing the beginning of hidden
name after a ‘.’, e.g. ‘_’. This allows access to modules with
<codeclass="docutils literal"><spanclass="pre">__all__</span></code> set, or to class-private attributes.</p>
<p>Completions and the ‘Expand Word’ facility can save a lot of typing!</p>
<p>“Hidden” attributes can be accessed by typing the beginning of hidden
name after a ‘.’, e.g. ‘_’. This allows access to modules with
<codeclass="docutils literal notranslate"><spanclass="pre">__all__</span></code> set, or to class-private attributes.</p>
<p>Completions and the ‘Expand Word’ facility can save a lot of typing!</p>
<p>Completions are currently limited to those in the namespaces. Names in
an Editor window which are not via <codeclass="docutils literal"><spanclass="pre">__main__</span></code> and <aclass="reference internal"href="sys.html#sys.modules"title="sys.modules"><codeclass="xref py py-data docutils literal"><spanclass="pre">sys.modules</span></code></a> will
an Editor window which are not via <codeclass="docutils literal notranslate"><spanclass="pre">__main__</span></code> and <aclass="reference internal"href="sys.html#sys.modules"title="sys.modules"><codeclass="xref py py-data docutils literal notranslate"><spanclass="pre">sys.modules</span></code></a> will
not be found. Run the module once with your imports to correct this situation.
Note that IDLE itself places quite a few modules in sys.modules, so
much can be found by default, e.g. the re module.</p>
<p>If you don’t like the ACW popping up unbidden, simply make the delay
<p>If you don’t like the ACW popping up unbidden, simply make the delay
longer or disable the extension.</p>
</div>
<divclass="section"id="calltips">
<h3>25.5.2.3. Calltips<aclass="headerlink"href="#calltips"title="Permalink to this headline">¶</a></h3>
<p>A calltip is shown when one types <codeclass="kbd docutils literal"><spanclass="pre">(</span></code> after the name of an <em>accessible</em>
<h3>26.5.2.3. Calltips<aclass="headerlink"href="#calltips"title="Permalink to this headline">¶</a></h3>
<p>A calltip is shown when one types <kbdclass="kbd docutils literal notranslate">(</kbd> after the name of an <em>accessible</em>
function. A name expression may include dots and subscripts. A calltip
remains until it is clicked, the cursor is moved out of the argument area,
or <codeclass="kbd docutils literal"><spanclass="pre">)</span></code> is typed. When the cursor is in the argument part of a definition,
or <kbdclass="kbd docutils literal notranslate">)</kbd> is typed. When the cursor is in the argument part of a definition,
the menu or shortcut display a calltip.</p>
<p>A calltip consists of the function signature and the first line of the
docstring. For builtins without an accessible signature, the calltip
...
...
@@ -457,40 +454,40 @@ details may change.</p>
<p>The set of <em>accessible</em> functions depends on what modules have been imported
into the user process, including those imported by Idle itself,
and what definitions have been run, all since the last restart.</p>
<p>For example, restart the Shell and enter <codeclass="docutils literal"><spanclass="pre">itertools.count(</span></code>. A calltip
<p>For example, restart the Shell and enter <codeclass="docutils literal notranslate"><spanclass="pre">itertools.count(</span></code>. A calltip
appears because Idle imports itertools into the user process for its own use.
(This could change.) Enter <codeclass="docutils literal"><spanclass="pre">turtle.write(</span></code> and nothing appears. Idle does
(This could change.) Enter <codeclass="docutils literal notranslate"><spanclass="pre">turtle.write(</span></code> and nothing appears. Idle does
not import turtle. The menu or shortcut do nothing either. Enter
<codeclass="docutils literal"><spanclass="pre">import</span><spanclass="pre">turtle</span></code> and then <codeclass="docutils literal"><spanclass="pre">turtle.write(</span></code> will work.</p>
<codeclass="docutils literal notranslate"><spanclass="pre">import</span><spanclass="pre">turtle</span></code> and then <codeclass="docutils literal notranslate"><spanclass="pre">turtle.write(</span></code> will work.</p>
<p>In an editor, import statements have no effect until one runs the file. One
might want to run a file after writing the import statements at the top,
or immediately run an existing file before editing.</p>
</div>
<divclass="section"id="python-shell-window">
<h3>25.5.2.4. Python Shell window<aclass="headerlink"href="#python-shell-window"title="Permalink to this headline">¶</a></h3>
<h3>26.5.2.4. Python Shell window<aclass="headerlink"href="#python-shell-window"title="Permalink to this headline">¶</a></h3>
<li><pclass="first"><codeclass="kbd docutils literal"><spanclass="pre">C-d</span></code> sends end-of-file; closes window if typed at a <codeclass="docutils literal"><spanclass="pre">>>></span></code> prompt</p>
<li><pclass="first"><kbdclass="kbd docutils literal notranslate">C-d</kbd> sends end-of-file; closes window if typed at a <codeclass="docutils literal notranslate"><spanclass="pre">>>></span></code> prompt</p>
</li>
<li><pclass="first"><codeclass="kbd docutils literal"><spanclass="pre">Alt-/</span></code> (Expand word) is also useful to reduce typing</p>
<li><pclass="first"><kbdclass="kbd docutils literal notranslate">Alt-/</kbd> (Expand word) is also useful to reduce typing</p>
<p>Command history</p>
<ulclass="simple">
<li><codeclass="kbd docutils literal"><spanclass="pre">Alt-p</span></code> retrieves previous command matching what you have typed. On
OS X use <codeclass="kbd docutils literal"><spanclass="pre">C-p</span></code>.</li>
<li><codeclass="kbd docutils literal"><spanclass="pre">Alt-n</span></code> retrieves next. On OS X use <codeclass="kbd docutils literal"><spanclass="pre">C-n</span></code>.</li>
<li><codeclass="kbd docutils literal"><spanclass="pre">Return</span></code> while on any previous command retrieves that command</li>
<li><kbdclass="kbd docutils literal notranslate">Alt-p</kbd> retrieves previous command matching what you have typed. On
OS X use <kbdclass="kbd docutils literal notranslate">C-p</kbd>.</li>
<li><kbdclass="kbd docutils literal notranslate">Alt-n</kbd> retrieves next. On OS X use <kbdclass="kbd docutils literal notranslate">C-n</kbd>.</li>
<li><kbdclass="kbd docutils literal notranslate">Return</kbd> while on any previous command retrieves that command</li>
</ul>
</li>
</ul>
</div>
<divclass="section"id="text-colors">
<h3>25.5.2.5. Text colors<aclass="headerlink"href="#text-colors"title="Permalink to this headline">¶</a></h3>
<h3>26.5.2.5. Text colors<aclass="headerlink"href="#text-colors"title="Permalink to this headline">¶</a></h3>
<p>Idle defaults to black on white text, but colors text with special meanings.
For the shell, these are shell output, shell error, user output, and
user error. For Python code, at the shell prompt or in an editor, these are
keywords, builtin class and function names, names following <codeclass="docutils literal"><spanclass="pre">class</span></code> and
<codeclass="docutils literal"><spanclass="pre">def</span></code>, strings, and comments. For any text window, these are the cursor (when
keywords, builtin class and function names, names following <codeclass="docutils literal notranslate"><spanclass="pre">class</span></code> and
<codeclass="docutils literal notranslate"><spanclass="pre">def</span></code>, strings, and comments. For any text window, these are the cursor (when
present), found text (when possible), and selected text.</p>
<p>Text coloring is done in the background, so uncolorized text is occasionally
visible. To change the color scheme, use the Configure IDLE dialog
...
...
@@ -499,22 +496,22 @@ text in popups and dialogs is not user-configurable.</p>
<h2>25.5.3. Startup and code execution<aclass="headerlink"href="#startup-and-code-execution"title="Permalink to this headline">¶</a></h2>
<p>Upon startup with the <codeclass="docutils literal"><spanclass="pre">-s</span></code> option, IDLE will execute the file referenced by
the environment variables <spanclass="target"id="index-5"></span><codeclass="xref std std-envvar docutils literal"><spanclass="pre">IDLESTARTUP</span></code> or <spanclass="target"id="index-6"></span><aclass="reference internal"href="../using/cmdline.html#envvar-PYTHONSTARTUP"><codeclass="xref std std-envvar docutils literal"><spanclass="pre">PYTHONSTARTUP</span></code></a>.
IDLE first checks for <codeclass="docutils literal"><spanclass="pre">IDLESTARTUP</span></code>; if <codeclass="docutils literal"><spanclass="pre">IDLESTARTUP</span></code> is present the file
referenced is run. If <codeclass="docutils literal"><spanclass="pre">IDLESTARTUP</span></code> is not present, IDLE checks for
<codeclass="docutils literal"><spanclass="pre">PYTHONSTARTUP</span></code>. Files referenced by these environment variables are
<h2>26.5.3. Startup and code execution<aclass="headerlink"href="#startup-and-code-execution"title="Permalink to this headline">¶</a></h2>
<p>Upon startup with the <codeclass="docutils literal notranslate"><spanclass="pre">-s</span></code> option, IDLE will execute the file referenced by
the environment variables <spanclass="target"id="index-5"></span><codeclass="xref std std-envvar docutils literal notranslate"><spanclass="pre">IDLESTARTUP</span></code> or <spanclass="target"id="index-6"></span><aclass="reference internal"href="../using/cmdline.html#envvar-PYTHONSTARTUP"><codeclass="xref std std-envvar docutils literal notranslate"><spanclass="pre">PYTHONSTARTUP</span></code></a>.
IDLE first checks for <codeclass="docutils literal notranslate"><spanclass="pre">IDLESTARTUP</span></code>; if <codeclass="docutils literal notranslate"><spanclass="pre">IDLESTARTUP</span></code> is present the file
referenced is run. If <codeclass="docutils literal notranslate"><spanclass="pre">IDLESTARTUP</span></code> is not present, IDLE checks for
<codeclass="docutils literal notranslate"><spanclass="pre">PYTHONSTARTUP</span></code>. Files referenced by these environment variables are
convenient places to store functions that are used frequently from the IDLE
shell, or for executing import statements to import common modules.</p>
<p>In addition, <codeclass="docutils literal"><spanclass="pre">Tk</span></code> also loads a startup file if it is present. Note that the
Tk file is loaded unconditionally. This additional file is <codeclass="docutils literal"><spanclass="pre">.Idle.py</span></code> and is
looked for in the user’s home directory. Statements in this file will be
<p>In addition, <codeclass="docutils literal notranslate"><spanclass="pre">Tk</span></code> also loads a startup file if it is present. Note that the
Tk file is loaded unconditionally. This additional file is <codeclass="docutils literal notranslate"><spanclass="pre">.Idle.py</span></code> and is
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.</p>
functions to be used from IDLE’s Python shell.</p>
<divclass="section"id="command-line-usage">
<h3>25.5.3.1. Command line usage<aclass="headerlink"href="#command-line-usage"title="Permalink to this headline">¶</a></h3>
@@ -529,21 +526,21 @@ functions to be used from IDLE’s Python shell.</p>
</div>
<p>If there are arguments:</p>
<ulclass="simple">
<li>If <codeclass="docutils literal"><spanclass="pre">-</span></code>, <codeclass="docutils literal"><spanclass="pre">-c</span></code>, or <codeclass="docutils literal"><spanclass="pre">r</span></code> is used, all arguments are placed in
<codeclass="docutils literal"><spanclass="pre">sys.argv[1:...]</span></code> and <codeclass="docutils literal"><spanclass="pre">sys.argv[0]</span></code> is set to <codeclass="docutils literal"><spanclass="pre">''</span></code>, <codeclass="docutils literal"><spanclass="pre">'-c'</span></code>,
or <codeclass="docutils literal"><spanclass="pre">'-r'</span></code>. No editor window is opened, even if that is the default
<li>If <codeclass="docutils literal notranslate"><spanclass="pre">-</span></code>, <codeclass="docutils literal notranslate"><spanclass="pre">-c</span></code>, or <codeclass="docutils literal notranslate"><spanclass="pre">r</span></code> is used, all arguments are placed in
<codeclass="docutils literal notranslate"><spanclass="pre">sys.argv[1:...]</span></code> and <codeclass="docutils literal notranslate"><spanclass="pre">sys.argv[0]</span></code> is set to <codeclass="docutils literal notranslate"><spanclass="pre">''</span></code>, <codeclass="docutils literal notranslate"><spanclass="pre">'-c'</span></code>,
or <codeclass="docutils literal notranslate"><spanclass="pre">'-r'</span></code>. No editor window is opened, even if that is the default
set in the Options dialog.</li>
<li>Otherwise, arguments are files opened for editing and
<codeclass="docutils literal"><spanclass="pre">sys.argv</span></code> reflects the arguments passed to IDLE itself.</li>
<codeclass="docutils literal notranslate"><spanclass="pre">sys.argv</span></code> reflects the arguments passed to IDLE itself.</li>
</ul>
</div>
<divclass="section"id="startup-failure">
<h3>25.5.3.2. Startup failure<aclass="headerlink"href="#startup-failure"title="Permalink to this headline">¶</a></h3>
<h3>26.5.3.2. Startup failure<aclass="headerlink"href="#startup-failure"title="Permalink to this headline">¶</a></h3>
<p>IDLE uses a socket to communicate between the IDLE GUI process and the user
code execution process. A connection must be established whenever the Shell
starts or restarts. (The latter is indicated by a divider line that says
‘RESTART’). If the user process fails to connect to the GUI process, it
displays a <codeclass="docutils literal"><spanclass="pre">Tk</span></code> error box with a ‘cannot connect’ message that directs the
‘RESTART’). If the user process fails to connect to the GUI process, it
displays a <codeclass="docutils literal notranslate"><spanclass="pre">Tk</span></code> error box with a ‘cannot connect’ message that directs the
user here. It then exits.</p>
<p>A common cause of failure is a user-written file with the same name as a
standard library module, such as <em>random.py</em> and <em>tkinter.py</em>. When such a
...
...
@@ -565,46 +562,46 @@ Manager to detect and stop one. Sometimes a restart initiated by a program
crash or Keyboard Interrupt (control-C) may fail to connect. Dismissing
the error box or Restart Shell on the Shell menu may fix a temporary problem.</p>
<p>When IDLE first starts, it attempts to read user configuration files in
~/.idlerc/ (~ is one’s home directory). If there is a problem, an error
~/.idlerc/ (~ is one’s home directory). If there is a problem, an error
message should be displayed. Leaving aside random disk glitches, this can
be prevented by never editing the files by hand, using the configuration
dialog, under Options, instead Options. Once it happens, the solution may
be to delete one or more of the configuration files.</p>
<p>If IDLE quits with no message, and it was not started from a console, try
starting from a console (<codeclass="docutils literal"><spanclass="pre">python</span><spanclass="pre">-m</span><spanclass="pre">idlelib)</span></code> and see if a message appears.</p>
starting from a console (<codeclass="docutils literal notranslate"><spanclass="pre">python</span><spanclass="pre">-m</span><spanclass="pre">idlelib)</span></code> and see if a message appears.</p>
</div>
<divclass="section"id="idle-console-differences">
<h3>25.5.3.3. IDLE-console differences<aclass="headerlink"href="#idle-console-differences"title="Permalink to this headline">¶</a></h3>
<h3>26.5.3.3. IDLE-console differences<aclass="headerlink"href="#idle-console-differences"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.
However, the different interface and operation occasionally affect
visible results. For instance, <codeclass="docutils literal"><spanclass="pre">sys.modules</span></code> starts with more entries.</p>
<p>IDLE also replaces <codeclass="docutils literal"><spanclass="pre">sys.stdin</span></code>, <codeclass="docutils literal"><spanclass="pre">sys.stdout</span></code>, and <codeclass="docutils literal"><spanclass="pre">sys.stderr</span></code> with
visible results. For instance, <codeclass="docutils literal notranslate"><spanclass="pre">sys.modules</span></code> starts with more entries.</p>
<p>IDLE also replaces <codeclass="docutils literal notranslate"><spanclass="pre">sys.stdin</span></code>, <codeclass="docutils literal notranslate"><spanclass="pre">sys.stdout</span></code>, and <codeclass="docutils literal notranslate"><spanclass="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
normally transparent, but functions that directly access the keyboard
and screen will not work. If <codeclass="docutils literal"><spanclass="pre">sys</span></code> is reset with <codeclass="docutils literal"><spanclass="pre">importlib.reload(sys)</span></code>,
IDLE’s changes are lost and things like <codeclass="docutils literal"><spanclass="pre">input</span></code>, <codeclass="docutils literal"><spanclass="pre">raw_input</span></code>, and
<codeclass="docutils literal"><spanclass="pre">print</span></code> will not work correctly.</p>
<p>With IDLE’s Shell, one enters, edits, and recalls complete statements.
and screen will not work. If <codeclass="docutils literal notranslate"><spanclass="pre">sys</span></code> is reset with <codeclass="docutils literal notranslate"><spanclass="pre">importlib.reload(sys)</span></code>,
IDLE’s changes are lost and things like <codeclass="docutils literal notranslate"><spanclass="pre">input</span></code>, <codeclass="docutils literal notranslate"><spanclass="pre">raw_input</span></code>, and
<codeclass="docutils literal notranslate"><spanclass="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
<codeclass="docutils literal"><spanclass="pre">exec</span></code> to run each statement. As a result, <codeclass="docutils literal"><spanclass="pre">'__builtins__'</span></code> is always
<codeclass="docutils literal notranslate"><spanclass="pre">exec</span></code> to run each statement. As a result, <codeclass="docutils literal notranslate"><spanclass="pre">'__builtins__'</span></code> is always
<h3>25.5.3.4. Developing tkinter applications<aclass="headerlink"href="#developing-tkinter-applications"title="Permalink to this headline">¶</a></h3>
<h3>26.5.3.4. Developing tkinter applications<aclass="headerlink"href="#developing-tkinter-applications"title="Permalink to this headline">¶</a></h3>
<p>IDLE is intentionally different from standard Python in order to
facilitate development of tkinter programs. Enter <codeclass="docutils literal"><spanclass="pre">import</span><spanclass="pre">tkinter</span><spanclass="pre">as</span><spanclass="pre">tk;</span>
facilitate development of tkinter programs. Enter <codeclass="docutils literal notranslate"><spanclass="pre">import</span><spanclass="pre">tkinter</span><spanclass="pre">as</span><spanclass="pre">tk;</span>
<spanclass="pre">root</span><spanclass="pre">=</span><spanclass="pre">tk.Tk()</span></code> in standard Python and nothing appears. Enter the same
in IDLE and a tk window appears. In standard Python, one must also enter
<codeclass="docutils literal"><spanclass="pre">root.update()</span></code> to see the window. IDLE does the equivalent in the
<codeclass="docutils literal notranslate"><spanclass="pre">root.update()</span></code> to see the window. IDLE does the equivalent in the
background, about 20 times a second, which is about every 50 milleseconds.
Next enter <codeclass="docutils literal"><spanclass="pre">b</span><spanclass="pre">=</span><spanclass="pre">tk.Button(root,</span><spanclass="pre">text='button');</span><spanclass="pre">b.pack()</span></code>. Again,
nothing visibly changes in standard Python until one enters <codeclass="docutils literal"><spanclass="pre">root.update()</span></code>.</p>
<p>Most tkinter programs run <codeclass="docutils literal"><spanclass="pre">root.mainloop()</span></code>, which usually does not
Next enter <codeclass="docutils literal notranslate"><spanclass="pre">b</span><spanclass="pre">=</span><spanclass="pre">tk.Button(root,</span><spanclass="pre">text='button');</span><spanclass="pre">b.pack()</span></code>. Again,
nothing visibly changes in standard Python until one enters <codeclass="docutils literal notranslate"><spanclass="pre">root.update()</span></code>.</p>
<p>Most tkinter programs run <codeclass="docutils literal notranslate"><spanclass="pre">root.mainloop()</span></code>, which usually does not
return until the tk app is destroyed. If the program is run with
<codeclass="docutils literal"><spanclass="pre">python</span><spanclass="pre">-i</span></code> or from an IDLE editor, a <codeclass="docutils literal"><spanclass="pre">>>></span></code> shell prompt does not
appear until <codeclass="docutils literal"><spanclass="pre">mainloop()</span></code> returns, at which time there is nothing left
<codeclass="docutils literal notranslate"><spanclass="pre">python</span><spanclass="pre">-i</span></code> or from an IDLE editor, a <codeclass="docutils literal notranslate"><spanclass="pre">>>></span></code> shell prompt does not
appear until <codeclass="docutils literal notranslate"><spanclass="pre">mainloop()</span></code> returns, at which time there is nothing left
to interact with.</p>
<p>When running a tkinter program from an IDLE editor, one can comment out
the mainloop call. One then gets a shell prompt immediately and can
...
...
@@ -612,7 +609,7 @@ interact with the live application. One just has to remember to
re-enable the mainloop call when running in standard Python.</p>
