Execute a Python script
So far we have played around with Python commands in the Python shell. We want to write now our first serious Python program. You will hardly find any beginner's textbook on programming, which don't start with the "nearly mandatory" "Hello World" program, i.e. a program which prints the string "Hello World". This looks on the Python shell like this:
$ python3 Python 3.4.0 (default, Apr 11 2014, 13:05:11) [GCC 4.8.2] on linux Type "help", "copyright", "credits" or "license" for more information. >>> print("Hello World!") Hello World! >>>But, as we said at the beginning, we want to write a "serious" script now. We use a slight variation of the "Hello World" theme. We have to include our print statement into a file. To save and edit our program in a file we need an editor. There are lots of editors, but you should choose one, which supports syntax highlighting and indentation. Under Linux you can use vi, vim, emacs, geany, gedit and umpteen others. The emacs works under windows as well, but notepad++ may be the better choice in many cases.
So, after you have found the editor of your choice, you can input your mini script, i.e.
print("My first simple Python script!")and save it as my_first_simple_script.py.
The suffix .py is not really necessary under Linux but it's good style to use it. But the extension is essential, if you want to write modules.
Start a Python script
Let's assume our script is in a subdirectory under the home directory of user monty:
monty@python:~$ cd python monty@python:~/python$ python my_first_simple_script.py My first simple Python script! monty@python:~/python$
It can be started under Windows in a Command prompt (start -> All Programs -> Accessories -> Command Prompt):
Python InternalsMost probably you will have read somewhere that the Python language is an interpreted programming or a script language. The truth is: Python is both an interpreted and a compiled language. But calling Python a compiled language would be misleading. (At the end of this chapter, you will find the definitions for Compilers and Interpreters, if you are not familiar with the concepts!) People would assume that the compiler translates the Python code into machine language. Python code is translated into intermediate code, which has to be executed by a virtual machine, known as the PVM, the Python virtual machine. This is a similar approach to the one taken by Java. There is even a way of translating Python programs into Java byte code for the Java Virtual Machine (JVM). This can be achieved with Jython.
The question is, do I have to compile my Python scripts to make them faster or how can I compile them? The answer is easy: Normally, you don't need to do anything and you shouldn't bother, because "Python" is doing the thinking for you, i.e. it takes the necessary steps automatically.
For whatever reason you want to compile a python program manually? No problem. It can be done with the module py_compile, either using the interpreter shell
>>> import py_compile >>> py_compile.compile('my_first_simple_script.py') >>>or using the following command at the shell prompt
python -m py_compile my_first_simple_script.pyEither way, you may notice two things: First, there will be a new subdirectory "__pycache__", if it hasn't already existed. You will find a file "my_first_simple_script.cpython-34.pyc" in this subdirectory. This is the compiled version of our file in byte code.
You can also automatically compile all Python files using the compileall module. You can do it from the shell prompt by running compileall.py and providing the path of the directory containing the Python files to compile:
monty@python:~/python$ python -m compileall . Listing . ...
But as we have said, you don't have to and shouldn't bother about compiling Python code. The compilation is hidden from the user for a good reason. Some newbies to Python wonder sometimes where these ominous files with the .pyc suffix might come from. If Python has write-access for the directory where the Python program resides, it will store the compiled byte code in a file that ends with a .pyc suffix. If Python has no write access, the program will work anyway. The byte code will be produced but discarded when the program exits.
Whenever a Python program is called, Python will check, if there exists a compiled version with the .pyc suffix. This file has to be newer than the file with the .py suffix. If such a file exists, Python will load the byte code, which will speed up the start up time of the script. If there exists no byte code version, Python will create the byte code before it starts the execution of the program. Execution of a Python program means execution of the byte code on the Python Virtual Machine (PVM).
Every time a Python script is executed, byte code is created. If a Python script is
imported as a module, the byte code will be stored in the corresponding .pyc file.
So the following will not create a byte code file:
monty@python:~/python$ python my_first_simple_script.py My first simple Python script! monty@python:~/python$The import in the following Python2 session will create a byte code file with the name "my_first_simple_script.pyc":
monty@python:~/tmp$ ls my_first_simple_script.py monty@python:~/tmp$ python Python 2.6.5 (r265:79063, Apr 16 2010, 13:57:41) [GCC 4.4.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import my_first_simple_script My first simple Python script! >>> exit() monty@python:~/tmp$ ls my_first_simple_script.py my_first_simple_script.pyc monty@python:~/tmp$
Runnable Scripts under LinuxThis chapter can be skipped by Windows users. Don't worry! It is not essential!
So far, we have started our Python scripts with
python3 my_file.pyon the bash command line.
A Python script can also be started like any other script under Linux, e.g. Bash scripts. Two steps are necessary for this purpose:
- The shebang line
#!/usr/bin/env python3has to be added as the first line of your Python code file. Alternatively, this line can be
#!/usr/bin/python3, if this is the location of your Python interpreter. By instead using env as in the first shebang line, the interpreter is searched for and located at the time the script is run. This makes the script more portable. Yet, it also suffers from the same problem: The path to env may also be different on a per-machine basis.
- The file has to be made executable:
The command "chmod +x scriptname" has to be executed on a Linux shell, e.g. bash. "chmod 755 scriptname" can also be used to make your file executable. In our example:
$ chmod +x my_first_simple_script.py
bernd@saturn: $ more my_first_simple_script.py #!/usr/bin/env python3 print("My first simple Python script!") bernd@saturn: $ ls -l my_first_simple_script.py -rw-rw-r-- 1 bernd bernd 40 Feb 4 09:32 my_first_simple_script.py bernd@saturn: $ chmod +x my_first_simple_script.py bernd@saturn: $ ls -l my_first_simple_script.py -rwxrwxr-x 1 bernd bernd 40 Feb 4 09:32 my_first_simple_script.py My first simple Python script!
Differences between Compilers and Interpreters
Definition: A compiler is a computer program that transforms (translates) source code of a programming language (the source language) into another computer language (the target language). In most cases compilers are used to transform source code into executable program, i.e. they translate code from high-level programming languages into low (or lower) level languages, mostly assembly or machine code.
Definition: An interpreter is a computer program that executes instructions written in a programming language. It can either
- execute the source code directly or
- translates the source code in a first step into a more efficient representation and executes this code