Continuously Check the Value of a Variable Python
Watch Now This tutorial has a related video course created by the Real Python team. Watch it together with the written tutorial to deepen your understanding: Variables in Python
In the previous tutorial on Basic Data Types in Python, you saw how values of various Python data types can be created. But so far, all the values shown have been literal or constant values:
If you're writing more complex code, your program will need data that can change as program execution proceeds.
Here's what you'll learn in this tutorial: You will learn how every item of data in a Python program can be described by the abstract term object, and you'll learn how to manipulate objects using symbolic names called variables.
Variable Assignment
Think of a variable as a name attached to a particular object. In Python, variables need not be declared or defined in advance, as is the case in many other programming languages. To create a variable, you just assign it a value and then start using it. Assignment is done with a single equals sign (=):
This is read or interpreted as "n is assigned the value 300." Once this is done, n can be used in a statement or expression, and its value will be substituted:
Just as a literal value can be displayed directly from the interpreter prompt in a REPL session without the need for print(), so can a variable:
Later, if you change the value of n and use it again, the new value will be substituted instead:
>>>
>>> n = 1000 >>> print ( n ) 1000 >>> n 1000 Python also allows chained assignment, which makes it possible to assign the same value to several variables simultaneously:
>>>
>>> a = b = c = 300 >>> print ( a , b , c ) 300 300 300 The chained assignment above assigns 300 to the variables a, b, and c simultaneously.
Variable Types in Python
In many programming languages, variables are statically typed. That means a variable is initially declared to have a specific data type, and any value assigned to it during its lifetime must always have that type.
Variables in Python are not subject to this restriction. In Python, a variable may be assigned a value of one type and then later re-assigned a value of a different type:
>>>
>>> var = 23.5 >>> print ( var ) 23.5 >>> var = "Now I'm a string" >>> print ( var ) Now I'm a string Object References
What is actually happening when you make a variable assignment? This is an important question in Python, because the answer differs somewhat from what you'd find in many other programming languages.
Python is a highly object-oriented language. In fact, virtually every item of data in a Python program is an object of a specific type or class. (This point will be reiterated many times over the course of these tutorials.)
Consider this code:
When presented with the statement print(300), the interpreter does the following:
- Creates an integer object
- Gives it the value
300 - Displays it to the console
You can see that an integer object is created using the built-in type() function:
>>>
>>> type ( 300 ) <class 'int'> A Python variable is a symbolic name that is a reference or pointer to an object. Once an object is assigned to a variable, you can refer to the object by that name. But the data itself is still contained within the object.
For example:
This assignment creates an integer object with the value 300 and assigns the variable n to point to that object.
The following code verifies that n points to an integer object:
>>>
>>> print ( n ) 300 >>> type ( n ) <class 'int'> Now consider the following statement:
What happens when it is executed? Python does not create another object. It simply creates a new symbolic name or reference, m, which points to the same object that n points to.
Next, suppose you do this:
Now Python creates a new integer object with the value 400, and m becomes a reference to it.
Lastly, suppose this statement is executed next:
Now Python creates a string object with the value "foo" and makes n reference that.
There is no longer any reference to the integer object 300. It is orphaned, and there is no way to access it.
Tutorials in this series will occasionally refer to the lifetime of an object. An object's life begins when it is created, at which time at least one reference to it is created. During an object's lifetime, additional references to it may be created, as you saw above, and references to it may be deleted as well. An object stays alive, as it were, so long as there is at least one reference to it.
When the number of references to an object drops to zero, it is no longer accessible. At that point, its lifetime is over. Python will eventually notice that it is inaccessible and reclaim the allocated memory so it can be used for something else. In computer lingo, this process is referred to as garbage collection.
Object Identity
In Python, every object that is created is given a number that uniquely identifies it. It is guaranteed that no two objects will have the same identifier during any period in which their lifetimes overlap. Once an object's reference count drops to zero and it is garbage collected, as happened to the 300 object above, then its identifying number becomes available and may be used again.
The built-in Python function id() returns an object's integer identifier. Using the id() function, you can verify that two variables indeed point to the same object:
>>>
>>> n = 300 >>> m = n >>> id ( n ) 60127840 >>> id ( m ) 60127840 >>> m = 400 >>> id ( m ) 60127872 After the assignment m = n, m and n both point to the same object, confirmed by the fact that id(m) and id(n) return the same number. Once m is reassigned to 400, m and n point to different objects with different identities.
Deep Dive: Caching Small Integer Values
From what you now know about variable assignment and object references in Python, the following probably won't surprise you:
>>>
>>> m = 300 >>> n = 300 >>> id ( m ) 60062304 >>> id ( n ) 60062896With the statement
m = 300, Python creates an integer object with the value300and setsmas a reference to it.nis then similarly assigned to an integer object with value300—but not the same object. Thus, they have different identities, which you can verify from the values returned byid().But consider this:
>>>
>>> m = 30 >>> n = 30 >>> id ( m ) 1405569120 >>> id ( n ) 1405569120Here,
mandnare separately assigned to integer objects having value30. But in this case,id(m)andid(n)are identical!For purposes of optimization, the interpreter creates objects for the integers in the range
[-5, 256]at startup, and then reuses them during program execution. Thus, when you assign separate variables to an integer value in this range, they will actually reference the same object.
Variable Names
The examples you have seen so far have used short, terse variable names like m and n. But variable names can be more verbose. In fact, it is usually beneficial if they are because it makes the purpose of the variable more evident at first glance.
Officially, variable names in Python can be any length and can consist of uppercase and lowercase letters (A-Z, a-z), digits (0-9), and the underscore character (_). An additional restriction is that, although a variable name can contain digits, the first character of a variable name cannot be a digit.
For example, all of the following are valid variable names:
>>>
>>> name = "Bob" >>> Age = 54 >>> has_W2 = True >>> print ( name , Age , has_W2 ) Bob 54 True But this one is not, because a variable name can't begin with a digit:
>>>
>>> 1099 _filed = False SyntaxError: invalid token Note that case is significant. Lowercase and uppercase letters are not the same. Use of the underscore character is significant as well. Each of the following defines a different variable:
>>>
>>> age = 1 >>> Age = 2 >>> aGe = 3 >>> AGE = 4 >>> a_g_e = 5 >>> _age = 6 >>> age_ = 7 >>> _AGE_ = 8 >>> print ( age , Age , aGe , AGE , a_g_e , _age , age_ , _AGE_ ) 1 2 3 4 5 6 7 8 There is nothing stopping you from creating two different variables in the same program called age and Age, or for that matter agE. But it is probably ill-advised. It would certainly be likely to confuse anyone trying to read your code, and even you yourself, after you'd been away from it awhile.
It is worthwhile to give a variable a name that is descriptive enough to make clear what it is being used for. For example, suppose you are tallying the number of people who have graduated college. You could conceivably choose any of the following:
>>>
>>> numberofcollegegraduates = 2500 >>> NUMBEROFCOLLEGEGRADUATES = 2500 >>> numberOfCollegeGraduates = 2500 >>> NumberOfCollegeGraduates = 2500 >>> number_of_college_graduates = 2500 >>> print ( numberofcollegegraduates , NUMBEROFCOLLEGEGRADUATES , ... numberOfCollegeGraduates , NumberOfCollegeGraduates , ... number_of_college_graduates ) 2500 2500 2500 2500 2500 All of them are probably better choices than n, or ncg, or the like. At least you can tell from the name what the value of the variable is supposed to represent.
On the other hand, they aren't all necessarily equally legible. As with many things, it is a matter of personal preference, but most people would find the first two examples, where the letters are all shoved together, to be harder to read, particularly the one in all capital letters. The most commonly used methods of constructing a multi-word variable name are the last three examples:
- Camel Case: Second and subsequent words are capitalized, to make word boundaries easier to see. (Presumably, it struck someone at some point that the capital letters strewn throughout the variable name vaguely resemble camel humps.)
- Example:
numberOfCollegeGraduates
- Example:
- Pascal Case: Identical to Camel Case, except the first word is also capitalized.
- Example:
NumberOfCollegeGraduates
- Example:
- Snake Case: Words are separated by underscores.
- Example:
number_of_college_graduates
- Example:
Programmers debate hotly, with surprising fervor, which of these is preferable. Decent arguments can be made for all of them. Use whichever of the three is most visually appealing to you. Pick one and use it consistently.
You will see later that variables aren't the only things that can be given names. You can also name functions, classes, modules, and so on. The rules that apply to variable names also apply to identifiers, the more general term for names given to program objects.
The Style Guide for Python Code, also known as PEP 8, contains Naming Conventions that list suggested standards for names of different object types. PEP 8 includes the following recommendations:
- Snake Case should be used for functions and variable names.
- Pascal Case should be used for class names. (PEP 8 refers to this as the "CapWords" convention.)
Reserved Words (Keywords)
There is one more restriction on identifier names. The Python language reserves a small set of keywords that designate special language functionality. No object can have the same name as a reserved word.
In Python 3.6, there are 33 reserved keywords:
| Python Keywords | |||
|---|---|---|---|
False | def | if | raise |
None | del | import | return |
True | elif | in | try |
and | else | is | while |
as | except | lambda | with |
assert | finally | nonlocal | yield |
break | for | not | |
class | from | or | |
continue | global | pass |
You can see this list any time by typing help("keywords") to the Python interpreter. Reserved words are case-sensitive and must be used exactly as shown. They are all entirely lowercase, except for False, None, and True.
Trying to create a variable with the same name as any reserved word results in an error:
>>>
>>> for = 3 SyntaxError: invalid syntax Conclusion
This tutorial covered the basics of Python variables, including object references and identity, and naming of Python identifiers.
You now have a good understanding of some of Python's data types and know how to create variables that reference objects of those types.
Next, you will see how to combine data objects into expressions involving various operations.
Watch Now This tutorial has a related video course created by the Real Python team. Watch it together with the written tutorial to deepen your understanding: Variables in Python
Source: https://realpython.com/python-variables/
0 Response to "Continuously Check the Value of a Variable Python"
Post a Comment