About The Course Curriculum
About The Course Curriculum
The course also familiarizes the student with object-oriented approach. The course is
broken down into six modules.
Students who complete the course will be able to accomplish coding tasks related to the
basics of programming in the Python language, and to understand the fundamental
notions and techniques used in object-oriented programming.
Becoming PCAP certified ensures that the individual is fully acquainted with all the
primary means provided by Python 3 to enable her/him to start her/his own studies,
and to open a path to the developer's career.
Course Modules vs. PCEP and PCAP Certifications (click to enlarge)
Course syllabus
The course also familiarizes the student with object-oriented approach. The course is
broken down into six modules.
Students who complete the course will be able to accomplish coding tasks related to the
basics of programming in the Python language, and to understand the fundamental
notions and techniques used in object-oriented programming.
Becoming PCAP certified ensures that the individual is fully acquainted with all the
primary means provided by Python 3 to enable her/him to start her/his own studies,
and to open a path to the developer's career.
Course Modules vs. PCEP and PCAP Certifications (click to enlarge)
Course syllabus
Module 1
Introduction to Python and computer programming
Module 2
Data types, variables, basic input-output operations, basic operators
Module 3
Boolean values, conditional execution, loops, lists and list processing, logical and bitwise
operations
Module 4
Functions, tuples, dictionaries, and data processing
Computers are able to perform very complex tasks, but this ability is not innate. A
computer's nature is quite different.
It can execute only extremely simple operations, e.g., a computer cannot evaluate the
value of a complicated mathematical function by itself, although this isn't beyond the
realms of possibility in the near future.
Contemporary computers can only evaluate the results of very fundamental operations,
like adding or dividing, but they can do it very fast, and can repeat these actions virtually
any number of times.
Imagine that you want to know the average speed you've reached during a long journey.
You know the distance, you know the time, you need the speed.
Naturally, the computer will be able to compute this, but the computer is not aware of
such things as distance, speed or time. Therefore, it is necessary to instruct the computer
to:
These four simple actions form a program. Of course, these examples are not formalized,
and they are very far from what the computer can understand, but they are good enough
to be translated into a language the computer can accept.
Another language you use each day is your mother tongue, which you use to manifest
your will and to think about reality. Computers have their own language, too,
called machine language, which is very rudimentary.
The commands it recognizes are very simple. We can imagine that the computer responds
to orders like "take that number, divide by another and save the result".
No computer is currently capable of creating a new language. However, that may change soon. On the
other hand, people use a number of very different languages, too, but these languages developed
naturally. Moreover, they are still evolving.
New words are created every day and old words disappear. These languages are called natural
languages.
AN ALPHABET
a set of symbols used to build words of a certain language (e.g., the Latin alphabet for
English, the Cyrillic alphabet for Russian, Kanji for Japanese, and so on)
A LEXIS
(aka a dictionary) a set of words the language offers its users (e.g., the word "computer"
comes from the English language dictionary, while "cmoptrue" doesn't; the word "chat" is
present both in English and French dictionaries, but their meanings are different)
A SYNTAX
a set of rules (formal or informal, written or felt intuitively) used to determine if a certain
string of words forms a valid sentence (e.g., "I am a python" is a syntactically correct
phrase, while "I a python am" isn't)
SEMANTICS
a set of rules determining if a certain phrase makes sense (e.g., "I ate a doughnut" makes
sense, but "A doughnut ate me" doesn't)
The IL is, in fact, the alphabet of a machine language. This is the simplest and most
primary set of symbols we can use to give commands to a computer. It's the computer's
mother tongue.
Unfortunately, this tongue is a far cry from a human mother tongue. We all (both
computers and humans) need something else, a common language for computers and
humans, or a bridge between the two different worlds.
We need a language in which humans can write their programs and a language that
computers may use to execute the programs, one that is far more complex than machine
language and yet far simpler than natural language.
Such languages are often called high-level programming languages. They are at least
somewhat similar to natural ones in that they use symbols, words and conventions
readable to humans. These languages enable humans to express commands to computers
that are much more complex than those offered by ILs.
Unfortunately, a programmer can also make mistakes with each of the above four senses.
Each of them can cause the program to become completely useless.
Let's assume that you've successfully written a program. How do we persuade the
computer to execute it? You have to render your program into machine language. Luckily,
the translation can be done by a computer itself, making the whole process fast and
efficient.
There are two different ways of transforming a program from a high-level
programming language into machine language:
COMPILATION - the source program is translated once (however, this act must be
repeated each time you modify the source code) by getting a file (e.g., an .exe file if the
code is intended to be run under MS Windows) containing the machine code; now you can
distribute the file worldwide; the program that performs this translation is called a
compiler or translator;
INTERPRETATION - you (or any user of the code) can translate the source program each
time it has to be run; the program performing this kind of transformation is called an
interpreter, as it interprets the code every time it is intended to be executed; it also means
that you cannot just distribute the source code as-is, because the end-user also needs the
interpreter to execute it.
There are very few languages that can be both compiled and interpreted. Usually, a
programming language is projected with this factor in its constructors' minds - will it be
compiled or interpreted?
The interpreter reads the source code in a way that is common in Western culture: from
top to bottom and from left to right. There are some exceptions - they'll be covered later in
the course.
First of all, the interpreter checks if all subsequent lines are correct (using the four aspects
covered earlier).
If the compiler finds an error, it finishes its work immediately. The only result in this case is
an error message. The interpreter will inform you where the error is located and what
caused it. However, these messages may be misleading, as the interpreter isn't able to
follow your exact intentions, and may detect errors at some distance from their real
causes.
For example, if you try to use an entity of an unknown name, it will cause an error, but the
error will be discovered in the place where it tries to use the entity, not where the new
entity's name was introduced.
In other words, the actual reason is usually located a little earlier in the code, e.g., in the
place where you had to inform the interpreter that you were going to use the entity of the
name.
If the line looks good, the interpreter tries to execute it (note: each line is usually executed
separately, so the trio "read-check-execute" can be repeated many times - more times
than the actual number of lines in the source file, as some parts of the code may be
executed more than once).
It is also possible that a significant part of the code may be executed successfully before
the interpreter finds an error. This is normal behavior in this execution model.
You may ask now: which is better? The "compiling" model or the "interpreting" model?
There is no obvious answer. If there had been, one of these models would have ceased to
exist a long time ago. Both of them have their advantages and their disadvantages.
COMPILATION INTERPRETATION
the execution of the
translated code is
usually faster; you can run the code as soon as
only the user has to have you complete it - there are no
the compiler - the end- additional phases of translation;
user may use the code the code is stored using
without it; programming language, not the
ADVANTAGES the translated code is machine one - this means that it
stored using machine can be run on computers using
language - as it is very different machine languages;
hard to understand it, you don't compile your code
your own inventions and separately for each different
programming tricks are architecture.
likely to remain your
secret.
DISADVANTAGE the compilation itself don't expect that interpretation
S may be a very time- will ramp your code to high
consuming process - you speed - your code will share the
may not be able to run computer's power with the
COMPILATION INTERPRETATION
your code immediately
after any amendment; interpreter, so it can't be really
you have to have as fast;
many compilers as both you and the end user have
hardware platforms you to have the interpreter to run
want your code to be run your code.
on.
Python is an interpreted language. This means that it inherits all the described
advantages and disadvantages. Of course, it adds some of its unique features to
both sets.
If you want to program in Python, you'll need the Python interpreter. You won't
be able to run your code without it. Fortunately, Python is free. This is one of its
most important advantages.
What is Python?
Python is a widely-used, interpreted, object-oriented, and high-level programming
language with dynamic semantics, used for general-purpose programming.
And while you may know the python as a large snake, the name of the Python
programming language comes from an old BBC television comedy sketch series
called Monty Python's Flying Circus.
At the height of its success, the Monty Python team were performing their sketches to live
audiences across the world, including at the Hollywood Bowl.
Since Monty Python is considered one of the two fundamental nutrients to a programmer
(the other being pizza), Python's creator named the language in honor of the TV show.
There are not many languages whose authors are known by name. Python was created
by Guido van Rossum, born in 1956 in Haarlem, the Netherlands. Of course, Guido van
Rossum did not develop and evolve all the Python components himself.
The speed with which Python has spread around the world is a result of the continuous
work of thousands (very often anonymous) programmers, testers, users (many of them
aren't IT specialists) and enthusiasts, but it must be said that the very first idea (the seed
from which Python sprouted) came to one head - Guido's.
A hobby programming project
The circumstances in which Python was created are a bit puzzling. According to Guido van
Rossum:
In December 1989, I was looking for a "hobby" programming project that would keep me occupied
during the week around Christmas. My office (...) would be closed, but I had a home computer, and not
much else on my hands. I decided to write an interpreter for the new scripting language I had been
thinking about lately: a descendant of ABC that would appeal to Unix/C hackers. I chose Python as a
working title for the project, being in a slightly irreverent mood (and a big fan of Monty Python's Flying
Circus).Guido van Rossum
Python goals
In 1999, Guido van Rossum defined his goals for Python:
About 20 years later, it is clear that all these intentions have been fulfilled. Some sources
say that Python is the most popular programming language in the world, while others
claim it's the third or the fifth.
Either way, it still occupies a high rank in the top ten of the PYPL PopularitY of
Programming Language and the TIOBE Programming Community Index.
Python isn't a young language. It is mature and trustworthy. It's not a one-hit wonder.
It's a bright star in the programming firmament, and time spent learning Python is a very
good investment.
s Python special?
How does it happen that programmers, young and old, experienced and novice, want to
use it? How did it happen that large companies adopted Python and implemented their
flagship products using it?
There are many reasons - we've listed some of them already, but let's enumerate them
again in a more practical manner:
it's easy to learn - the time needed to learn Python is shorter than for many other
languages; this means that it's possible to start the actual programming faster;
it's easy to teach - the teaching workload is smaller than that needed by other
languages; this means that the teacher can put more emphasis on general
(language-independent) programming techniques, not wasting energy on exotic
tricks, strange exceptions and incomprehensible rules;
it's easy to use for writing new software - it's often possible to write code faster
when using Python;
it's easy to understand - it's also often easier to understand someone else's code
faster if it is written in Python;
it's easy to obtain, install and deploy - Python is free, open and multiplatform;
not all languages can boast that.
it's not a speed demon - Python does not deliver exceptional performance;
in some cases it may be resistant to some simpler testing techniques - this may
mean that debugging Python's code can be more difficult than with other
languages; fortunately, making mistakes is always harder in Python.
It should also be stated that Python is not the only solution of its kind available on the IT
market.
It has lots of followers, but there are many who prefer other languages and don't even
consider Python for their projects.
Python rivals?
Python has two direct competitors, with comparable properties and predispositions. These
are:
The former is more traditional, more conservative than Python, and resembles some of the
good old languages derived from the classic C programming language.
In contrast, the latter is more innovative and more full of fresh ideas than Python. Python
itself lies somewhere between these two creations.
The Internet is full of forums with infinite discussions on the superiority of one of these
three over the others, should you wish to learn more about each of them.
Python 2 is an older version of the original Python. Its development has since been
intentionally stalled, although that doesn't mean that there are no updates to it. On the
contrary, the updates are issued on a regular basis, but they are not intended to modify
the language in any significant way. They rather fix any freshly discovered bugs and
security holes. Python 2's development path has reached a dead end already, but Python 2
itself is still very much alive.
Python 3 is the newer (to be precise, the current) version of the language. It's
going through its own evolution path, creating its own standards and habits.
The former is more traditional, more conservative than Python, and resembles some of the
good old languages derived from the classic C programming language.
These two versions of Python aren't compatible with each other. Python 2 scripts won't run
in a Python 3 environment and vice versa, so if you want the old Python 2 code to be run
by a Python 3 interpreter, the only possible solution is to rewrite it, not from scratch, of
course, as large parts of the code may remain untouched, but you do have to revise all the
code to find all possible incompatibilities. Unfortunately, this process cannot be fully
automatized.
It's too hard, too time-consuming, too expensive, and too risky to migrate an old Python 2
application to a new platform. It's possible that rewriting the code will introduce new bugs
to it. It's easier and more sensible to leave these systems alone and to improve the
existing interpreter, instead of trying to work inside the already functioning source code.
NOTE
If you're going to start a new Python project, you should use Python 3, and this is the
version of Python that will be used during this course.
All the code samples you will find during the course have been tested against Python 3.4,
Python 3.6, and Python 3.7.
Python 2 is an older version of the original Python. Its development has since been
intentionally stalled, although that doesn't mean that there are no updates to it. On the
contrary, the updates are issued on a regular basis, but they are not intended to modify
the language in any significant way. They rather fix any freshly discovered bugs and
security holes. Python 2's development path has reached a dead end already, but Python 2
itself is still very much alive.
Python 3 is the newer (to be precise, the current) version of the language. It's
going through its own evolution path, creating its own standards and habits.
The former is more traditional, more conservative than Python, and resembles some of the
good old languages derived from the classic C programming language.
These two versions of Python aren't compatible with each other. Python 2 scripts won't run
in a Python 3 environment and vice versa, so if you want the old Python 2 code to be run
by a Python 3 interpreter, the only possible solution is to rewrite it, not from scratch, of
course, as large parts of the code may remain untouched, but you do have to revise all the
code to find all possible incompatibilities. Unfortunately, this process cannot be fully
automatized.
It's too hard, too time-consuming, too expensive, and too risky to migrate an old Python 2
application to a new platform. It's possible that rewriting the code will introduce new bugs
to it. It's easier and more sensible to leave these systems alone and to improve the
existing interpreter, instead of trying to work inside the already functioning source code.
If you're modifying an old existing Python solution, then it's highly likely that it was coded
in Python 2. This is the reason why Python 2 is still in use. There are too many existing
Python 2 applications to discard it altogether.
NOTE
If you're going to start a new Python project, you should use Python 3, and this is the
version of Python that will be used during this course.
All the code samples you will find during the course have been tested against Python 3.4,
Python 3.6, and Python 3.7.
"J" is for "Java". Imagine a Python written in Java instead of C. This is useful, for example, if
you develop large and complex systems written entirely in Java and want to add some
Python flexibility to them. The traditional CPython may be difficult to integrate into such an
environment, as C and Java live in completely different worlds and don't share many
common ideas.
Jython can communicate with existing Java infrastructure more effectively. This is why
some projects find it usable and needful.
Note: the current Jython implementation follows Python 2 standards. There is no Jython
conforming to Python 3, so far.
This is useful because if you want to test any new feature that may be (but doesn't have to
be) introduced into mainstream Python implementation, it's easier to check it with PyPy
than with CPython. This is why PyPy is rather a tool for people developing Python than for
the rest of the users.
This doesn't make PyPy any less important or less serious than CPython, of course.
There are many more different Pythons in the world. You'll find them if you look, but this
course will focus on CPython.
Linux users most probably have Python already installed - this is the most likely scenario, as
Python's infrastructure is intensively used by many Linux OS components.
For example, some distributors may couple their specific tools together with the system and many of
these tools, like package managers, are often written in Python. Some parts of graphical environments
available in the Linux world may use Python, too.
python3
If Python 3 is absent, then refer to your Linux documentation in order to find how to use your package
manager to download and install a new package - the one you need is named python3 or its name
begins with that.
In this case, select Python 3. The site always offers you the latest version of it.
If you're a Windows user, start the downloaded .exe file and follow all the steps.
Leave the default settings the installer suggests for now, with one exception - look at the
checkbox named Add Python 3.x to PATH and check it.
If you're a macOS user, a version of Python 2 may already have been preinstalled on your
computer, but since we will be working with Python 3, you will still need to download and
install the relevant .pkg file from the Python site.
Starting your work with Python
Now that you have Python 3 installed, it's time to check if it works and make the very first
use of it.
This will be a very simple procedure, but it should be enough to convince you that the
Python environment is complete and functional.
There are many ways of utilizing Python, especially if you're going to be a Python
developer.
Besides its many useful components, the Python 3 standard installation contains a very
simple but extremely useful application named IDLE.
Navigate through your OS menus, find IDLE somewhere under Python 3.x and launch it.
This is what you should see:
There are many ways of utilizing Python, especially if you're going to be a Python
developer.
an editor which will support you in writing the code (it should have some special
features, not available in simple tools); this dedicated editor will give you more than
the standard OS equipment;
a console in which you can launch your newly written code and stop it forcibly
when it gets out of control;
a tool named a debugger, able to launch your code step by step and allowing you
to inspect it at each moment of execution.
The first step is to create a new source file and fill it with code. Click File in the IDLE’s
menu and choose New file.
As you can see, IDLE opens a new window for you. You can use it to write and amend your
code.
This is the editor window. Its only purpose is to be a workplace in which your source
code is treated. Do not confuse the editor window with the shell window. They perform
different functions.
The editor window is currently untitled, but it's good practice to start work by naming the
source file.
Click File (in the new window), then click Save as..., select a folder for the new file (the
desktop is a good place for your first programming attempts) and chose a name for the
new file.
Note: don't set any extension for the file name you are going to use. Python needs its files
to have the .py extension, so you should rely on the dialog window's defaults. Using the
standard .py extension enables the OS to properly open these files.
You can use the clipboard to copy the text into the file.
We're not going to explain the meaning of the program right now. You'll find a detailed
discussion in the next chapter.
Take a closer look at the quotation marks. These are the simplest form of quotation marks
(neutral, straight, dumb, etc.) commonly used in source files. Do not try to use typographic
quotes (curved, curly, smart, etc.), used by advanced text processors, as Python doesn’t
accept them.
If everything goes okay and there are no mistakes in the code, the console window will
show you the effects caused by running the program.
Click File, Open, point to the file you saved previously and let IDLE read it in.
As you can see, IDLE is able to save your code and retrieve it when you need it again.
Remove the closing parenthesis again. The code becomes erroneous. It contains a syntax
error now. IDLE should not let you run it.
Try to run the program again. IDLE will remind you to save the modified file. Follow the
instructions.
A new window appears – it says that the interpreter has encountered an EOF (end-of-file)
although (in its opinion) the code should contain some more text.
print("Hisssssss...")
Let's spoil the code one more time. Remove one letter from the word print. Run the code
by pressing F5. As you can see, Python is not able to recognize the error.
How to spoil and fix your code
You may have noticed that the error message generated for the previous error is quite
different from the first one.
This is because the nature of the error is different and the error is discovered at
a different stage of interpretation.
The editor window will not provide any useful information regarding the error, but the
console windows might.
the traceback (which is the path that the code traverses through different parts of
the program - you can ignore it for now, as it is empty in such a simple code);
the location of the error (the name of the file containing the error, line number
and module name); note: the number may be misleading, as Python usually shows
the place where it first notices the effects of the error, not necessarily the error
itself;
the content of the erroneous line; note: IDLE’s editor window doesn’t show line
numbers, but it displays the current cursor location at the bottom-right corner; use
it to locate the erroneous line in a long source code;
the name of the error and a short explanation.
Experiment with creating new files and running your code. Try to output a different
message to the screen, e.g., roar! , meow , or even maybe an oink! . Try to spoil and fix
your code - see what happens.
Sandbox
This course does not require you to install any software applications to test your code and
do the exercises.
To test or experiment with your code, you can use a dedicated, interactive on-line
programming environment.
It is a tool integrated within the course, which can be used as a browser-based Python
sandbox that allows you to test code discussed throughout the course, as well as an
interpreter that enables you to launch, perform and test the lab
exercises specifically designed for this course.
The Sandbox interface consists of three main parts:
print("Hello!")
...then click the Sandbox button to enter Sandbox Mode, paste the code in the editor
window, and click the Run button to see what happens.
To get back to our course, click Back to course in the top right-hand corner of the
Sandbox interface.
Practice Interface
This course contains four different types of interfaces.
So far you've seen the Study Interface (one or two windows with text and images/animation),
and Sandbox Interface, which you can use to try out your own code (click Sandbox to switch to the
Sandbox Interface).
The one you see now is the Practice Interface, which enables you to study new things and do coding
tasks at the same time. You will use this kind of interface for most of the time during the course.
The Practice Interface consists of a text area on the left and the Editor/Console windows on the right.
One more type of interface that you will see in the future is the Quiz/Test Interface, which will let you
check your knowledge and skills to see how well you have mastered the study material.
PCEP - Certified Entry-Level Python Programmer certification shows that you are familiar
with universal computer programming concepts like data types, containers, functions,
conditions, and loops, as well as Python programming language syntax, semantics, and
the runtime environment.
Becoming PCEP certified ensures that you are acquainted with the most essential means
provided by Python 3 to enable you to start your own studies at an intermediate level and
to continue your professional development.
PCEP certification allows you to demonstrate that not only are you up to date with Python-
related issues, but also that you can competently deal with them. Furthermore, with the
OpenEDG Python Institute, you gain access to a large network of Python programming
professionals, a valuable resource for solving Python-related problems, and for developing
innovative solutions.
Get your foot in the door with the PCEP - Certified Entry-Level Python
Programmer certification. Land an entry-level programming job, break into the field, and
gain the necessary skills, knowledge, and experience to advance your career.