This week will effectively be a "crash-course" in Python basics; there's a lot of ground to cover!
We saw in the last lecture how to define variables, as well as a few of the basic variable "types" available in Python. It's important to keep in mind that each variable you define has a "type", and this type will dictate much (if not all) of the operations you can perform on and with that variable.
To recap: a variable in Python is a sort of placeholder that stores a value. Critically, a variable has both a name and a type. For example:
In [ ]:
x = 2
It's easy to determine the name of the variable; in this case, the name is $x$. It can be a bit more complicated to determine the type of the variable, as it depends on the value the variable is storing. In this case, it's storing the number 2. Since there's no decimal point on the number, we call this number an integer, or int for short.
In [12]:
y = 2.0
y is assigned a value of 2.0: it is referred to as a floating-point variable, or float for short.
Floats do the heavy-lifting of much of the computation in data science. Whenever you're computing probabilities or fractions or normalizations, floats are the types of variables you're using. In general, you tend to use floats for heavy computation, and ints for counting things.
There is an explicit connection between ints and floats. Let's illustrate with an example:
In [13]:
x = 2
y = 3
z = x / y
In this case, we've defined two variables x and y and assigned them integer values, so they are both of type int. However, we've used them both in a division operation and assigned the result to a variable named z. If we were to check the type of z, what type do you think it would be?
z is a float!
In [14]:
type(z)
Out[14]:
How does that happen? Shouldn't an operation involving two ints produce an int?
In general, yes it does. However, in cases where a decimal number is outputted, Python implicitly "promotes" the variable storing the result.
This is known as casting, and it can take two forms: implicit casting (as we just saw), or explicit casting.
Implicit casting is done in such a way as to try to abide by "common sense": if you're dividing two numbers, you would all but expect to receive a fraction, or decimal, on the other end. If you're multiplying two numbers, the type of the output depends on the types of the inputs--two floats multiplied will likely produce a float, while two ints multiplied will produce an int.
In [15]:
x = 2
y = 3
z = x * y
type(z)
Out[15]:
In [16]:
x = 2.5
y = 3.5
z = x * y
type(z)
Out[16]:
Explicit casting, on the other hand, is a little trickier. In this case, it's you the programmer who are making explicit (hence the name) what type you want your variables to be.
Python has a couple special built-in functions for performing explicit casting on variables, and they're named what you would expect: int() for casting a variable as an int, and float for casting it as a float.
In [17]:
x = 2.5
y = 3.5
z = x * y
print("Float z:\t{}\nInteger z:\t{}".format(z, int(z)))
Any idea what's happening here?
With explicit casting, you are telling Python to override its default behavior. In doing so, it has to make some decisions as to how to do so in a way that still makes sense.
When you cast a float to an int, some information is lost; namely, the decimal. So the way Python handles this is by quite literally discarding the entire decimal portion.
In this way, even if your number was 9.999999999 and you perfomed an explicit cast to int(), Python would hand you back a 9.
Python as a language is known as dynamically typed. This means you don't have to specify the type of the variable when you define it; rather, Python infers the type based on how you've defined it and how you use it.
As we've already seen, Python creates a variable of type int when you assign it an integer number like 5, and it automatically converts the type to a float whenever the operations produce decimals.
Other languages, like C++ and Java, are statically typed, meaning in addition to naming a variable when it is declared, the programmer must also explicitly state the type of the variable.
Pros and cons of dynamic typing (as opposed to static typing)?
Pros:
Cons:
For type-checking, Python implements what is known as duck typing: if it walks like a duck and quacks like a duck, it's a duck.
This brings us to a concept known as type safety. This is an important point, especially in dynamically typed languages where the type is not explicitly set by the programmer: there are countless examples of nefarious hacking that has exploited a lack of type safety in certain applications in order to execute malicious code.
A particularly fun example is known as a roundoff error, or more specifically to our case, a representation error. This occurs when we are attempting to represent a value for which we simply don't have enough precision to accurately store.
One of the most popular examples of an overflow error was the Y2K bug.
In these cases, and especially in dynamically typed languages like Python, it is very important to know what types of variables you're working with and what the limitations of those types are.
In [18]:
x = "this is a string"
type(x)
Out[18]:
Unlike numerical types like ints and floats, you can't really perform arithmetic operations on strings, with one exception:
In [19]:
x = "some string"
y = "another string"
z = x + " " + y
print(z)
The + operator, when applied to strings, is called string concatenation.
This means that it glues or concatenates two strings together to create a new string. In this case, we took the string in x, concatenated it to an empty space " ", and concatenated that again to the string in y, storing the whole thing in a final string z.
Other than the + operator, the other arithmetic operations aren't defined for strings, so I wouldn't recommend trying them...
In [20]:
s = "2"
t = "divisor"
x = s / t
The error quite literally states: the division operator is not supported for the left-hand operand of type string divided by a right-hand operand also of type string. Put simply, Python can't divide a string by a string!
Casting, however, is alive and well with strings. In particular, if you know the string you're working with is a string representation of a number, you can cast it from a string to a numeric type:
In [21]:
s = "2"
x = int(s)
print("x = {} and has type {}.".format(x, type(x)))
And back again:
In [22]:
x = 2
s = str(x)
print("s = {} and has type {}.".format(s, type(s)))
Strings also have some useful methods that numeric types don't for doing some basic text processing.
In [23]:
s = "Some string with WORDS"
print(s.upper()) # make all the letters uppercase
print(s.lower()) # make all the letters lowercase
A very useful method that will come in handy later in the course when we do some text processing is strip().
Often when you're reading text from a file and splitting it into tokens, you're left with strings that have leading or trailing whitespace:
In [25]:
s1 = " python "
s2 = " python"
s3 = "python "
Anyone who looked at these three strings would say they're the same, but the whitespace before and after the word python in each of them results in Python treating them each as unique. Thankfully, we can use the strip method:
In [27]:
print("|" + s1.strip() + "|")
print("|" + s2.strip() + "|")
print("|" + s3.strip() + "|")
You can also delimit strings using either single-quotes or double-quotes. Either is fine and largely depends on your preference.
In [ ]:
s = "some string"
t = 'this also works'
Python also has a built-in method len() that can be used to return the length of a string. The length is simply the number of individual characters (including any whitespace) in the string.
In [41]:
s = "some string"
len(s)
Out[41]:
We can also compare variables! By comparing variables, we can ask whether two things are equal, or greater than or less than some other value.
This sort of true-or-false comparison gives rise to yet another type in Python: the boolean type. A variable of this type takes only two possible values: True or False.
Let's say we have two numeric variables, x and y, and want to check if they're equal. To do this, we use a variation of the assginment operator:
In [28]:
x = 2
y = 2
x == y
Out[28]:
Hooray! The == sign is the equality comparison operator, and it will return True or False depending on whether or not the two values are exactly equal.
This works for strings as well:
In [30]:
s1 = "a string"
s2 = "a string"
s1 == s2
Out[30]:
In [31]:
s3 = "another string"
s1 == s3
Out[31]:
We can also ask if variables are less than or greater than each other, using the < and > operators, respectively.
In [32]:
x = 1
y = 2
x < y
Out[32]:
In [33]:
x > y
Out[33]:
In a small twist of relative magnitude comparisons, we can also ask if something is less than or equal to or greater than or equal to some other value. To do this, in addition to the comparison operators < or >, we also add an equal sign:
In [35]:
x = 2
y = 3
x <= y
Out[35]:
In [36]:
x = 3
x <= y
Out[36]:
In [37]:
x = 3.00001
x <= y
Out[37]:
Interestingly, these operators also work for strings. Be careful, though: their behavior may be somewhat unexpected until you figure out what actual trick is happening:
In [39]:
s1 = "some string"
s2 = "another string"
s1 > s2
Out[39]:
In [40]:
s1 = "Some string"
s1 > s2
Out[40]:
Any idea how the comparison is being done? If you don't, that's perfectly ok: the upshot is, it's [almost] always a bad idea to do this sort of comparison with strings.
There are some rules regarding what can and cannot be used as a variable name.
Beyond those rules, there are guidelines.
All the letters a-z (upper and lowercase), the numbers 0-9, and underscores are at your disposal. Anything else is illegal. No special characters like pound signs, dollar signs, or percents are allowed. Hashtag alphanumerics only.
Numbers cannot be the first character of a variable name. message_1 is a perfectly valid variable name; however, 1_message is not and will throw an error.
Underscores are how Python programmers tend to "simulate" spaces in variable names, but simply put there's no way to name a variable with multiple words separated by spaces.
This might take some trial-and-error. Basically, if you try to name a variable print or float or str, you'll run into a lot of problems down the road.
Technically this isn't outlawed in Python--it's not a rule, but rather a guideline, and a very good one--but it will cause a lot of headaches later in your program.
These are not hard-and-fast rules, but rather suggestions to help "standardize" code and make it easier to read by people who aren't necessarily familiar with the code you've written.
I've been giving a lot of examples using variables named x, s, and so forth. This is bad. Don't do it--unless, for example, you're defining x and y to be points in a 2D coordinate axis, or as a counter; one-letter variable names for counters are quite common.
Outside of those narrow use-cases, the variable names should constitute a pithy description that reflects their function in your program. A variable storing a name, for example, could be name or even student_name, but don't go as far as to use the_name_of_the_student.
l or uppercase O.This is one of those annoying rules that largely only applies to one-letter variables: stay away from using letters that also bear striking resemblance to numbers. Naming your variable l or O may confuse downstream readers of your code, making them think you're sprinkling 1s and 0s throughout your code.
Java programmers may take umbrage with this point: the convention there is to useCamelCase for multi-word variable names.
Since Python takes quite a bit from the C language (and its back-end is implemented in C), it also borrows a lot of C conventions, one of which is to use underscores and all lowercase letters in variable names. So rather than multiWordVariable, we do multi_word_variable.
The one exception to this rule is when you define variables that are constant; that is, their values don't change over your entire program. In this case, the variable name is usually in all-caps. For example: PI = 3.14159.
The practice of pithy but precise variable naming strategies is known as "self-documenting code."
We've learned before that we can insert comments into our code to explain things that might otherwise be confusing:
In [42]:
# Adds two numbers that are initially strings by converting them to an int and a float,
# then converting the final result to an int and storing it in the variable x.
x = int(int("1345") + float("31.5"))
print(x)
Comments are important to good coding style and should be used often for clarification.
However, even more preferable to the liberal use of comments is a good variable naming convention. For instance, instead of naming a variable "x" or "y" or "c", give it a name that describes its purpose.
In [44]:
str_length = len("some string")
I could have used a comment to explain how this variable was storing the length of the string, but by naming the variable itself in terms of what it was doing, I don't even need such a comment. It's self-evident from the name itself what this variable is doing. Hence, self-documenting.
Whitespace (no, not that Whitespace)) is important in the Python language.
Some languages like C++ and Java use semi-colons to delineate the end of a single statement. Python, however, does not, but still needs some way to identify when we've reached the end of a statement.
In Python, it's the return key that denotes the end of a statement.
Returns, tabs, and spaces are all collectively known as "whitespace", and each can drastically change how your Python program runs. Especially when we get into loops, conditionals, and functions, this will become critical and may be the source of many insidious bugs.
For example, the following code won't run:
In [45]:
x = 5
x += 10
Python sees the indentation--it's important to Python in terms of delineating blocks of code--but in this case the indentation doesn't make any sense. It doesn't highlight a new function, or a conditional, or a loop. It's just "there", making it unexpected and hence causing the error.
This can be particularly pernicious when writing longer Python programs, full of functions and loops and conditionals, where the indentation of your code is constantly changing. For this reason, I am giving you the following mandate:
DO NOT MIX TABS AND SPACES!!!
If you're indenting your code using 2 spaces, ALWAYS USE SPACES.
If you're indenting your code using 4 spaces, ALWAYS USE SPACES.
If you're indenting your code with a single tab, ALWAYS USE TABS.
Mixing the two in the same file will cause ALL THE HEADACHES. Your code will crash but will be coy as to the reason why.
1: Multiply 2.1 and 3.1 in Python. What do you get? Why?
2: Let's say you want to know how many words are in a document (like the review question in the last lecture). What type of variable would we use to store that value, and why?
3: What does len() return for s = "string"? How about s = " string "? How about s = " string ".strip()?
4: Give an example of a variable name that is used to store the average area of a group of squares. What type would this variable be?
5: I'm opening up my favorite text editor to write a Python script. Should I configure it to use tabs or spaces?