GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||
GeezerVison is showing docs.python.org — 2. Using the Python Interpreter — Python 3.5.10 documentation
This document is for an old version of Python that is no longer supported.
You should upgrade, and read the
Python documentation for the current stable release.
2. Using the Python Interpreter¶2.1. Invoking the Interpreter¶The Python interpreter is usually installed as python3.5 to the shell. [1] Since the choice of the directory where the interpreter lives
is an installation option, other places are possible; check with your local
Python guru or system administrator. (E.g., On Windows machines, the Python installation is usually placed in
set path=%path%;C:\python35 Typing an end-of-file character (Control-D on Unix, Control-Z on
Windows) at the primary prompt causes the interpreter to exit with a zero exit
status. If that doesn’t work, you can exit the interpreter by typing the
following command: The interpreter’s line-editing features include interactive editing, history
substitution and code completion on systems that support readline. Perhaps the
quickest check to see whether command line editing is supported is typing
Control-P to the first Python prompt you get. If it beeps, you have command
line editing; see Appendix Interactive Input Editing and History Substitution for an introduction to the
keys. If nothing appears to happen, or if The interpreter operates somewhat like the Unix shell: when called with standard input connected to a tty device, it reads and executes commands interactively; when called with a file name argument or with a file as standard input, it reads and executes a script from that file. A second way of starting the interpreter is Some Python modules are also useful as scripts. These can be invoked using
When a script file is used, it is sometimes useful to be able to run the script
and enter interactive mode afterwards. This can be done by passing All command line options are described in Command line and environment. 2.1.1. Argument Passing¶When known to the interpreter, the script name and additional arguments
thereafter are turned into a list of strings and assigned to the 2.1.2. Interactive Mode¶When commands are read from a tty, the interpreter is said to be in interactive
mode. In this mode it prompts for the next command with the primary prompt,
usually three greater-than signs ( $ python3.5 Python 3.5 (default, Sep 16 2015, 09:25:04) [GCC 4.8.2] on linux Type "help", "copyright", "credits" or "license" for more information. >>> Continuation lines are needed when entering a multi-line construct. As an
example, take a look at this >>> the_world_is_flat = True >>> if the_world_is_flat: ... print("Be careful not to fall off!") ... Be careful not to fall off! For more on interactive mode, see Interactive Mode. 2.2. The Interpreter and Its Environment¶2.2.1. Source Code Encoding¶By default, Python source files are treated as encoded in UTF-8. In that encoding, characters of most languages in the world can be used simultaneously in string literals, identifiers and comments — although the standard library only uses ASCII characters for identifiers, a convention that any portable code should follow. To display all these characters properly, your editor must recognize that the file is UTF-8, and it must use a font that supports all the characters in the file. It is also possible to specify a different encoding for source files. In order
to do this, put one more special comment line right after the # -*- coding: encoding -*-
With that declaration, everything in the source file will be treated as having
the encoding encoding instead of UTF-8. The list of possible encodings can be
found in the Python Library Reference, in the section on For example, if your editor of choice does not support UTF-8 encoded files and insists on using some other encoding, say Windows-1252, you can write: # -*- coding: cp-1252 -*-
and still use all characters in the Windows-1252 character set in the source files. The special encoding comment must be in the first or second line within the file. Footnotes
© Copyright 2001-2025, Python Software Foundation.
The Python Software Foundation is a non-profit corporation. Please donate. Last updated on Apr 16, 2025. Found a bug? Created using Sphinx 1.8.4. | ||
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |