{"id":2419,"date":"2025-09-02T15:31:54","date_gmt":"2025-09-02T07:31:54","guid":{"rendered":"http:\/\/blue.yn.cn\/?p=2419"},"modified":"2025-11-01T21:43:38","modified_gmt":"2025-11-01T13:43:38","slug":"veriables","status":"publish","type":"post","link":"http:\/\/blue.yn.cn\/?p=2419","title":{"rendered":"2. Veriables"},"content":{"rendered":"

Variables, expressions, and statements<\/strong><\/p>\n

values and types<\/h3>\n

A value is one of the basic thing a program works with, like a letter or a number. The values we have seen so far are 1,2, and "hello world!"<\/p>\n

These values belong to different types: 2 is an integer, and "hello world!" is a string, so called because is contains a "string" of letters. You (and the interpreter)can identify strings because they are enclosed in quotation marks.<\/p>\n

The print<\/code> statements also works for integer. We use the python<\/code> command to start the interpreter.<\/p>\n

python\n>>> print(4)\n4<\/code><\/pre>\n
If you are not sure what type a value has, the interpreter can tell you.<\/p>\n
>>> type('Hello,world!')\n<class 'str'>\n>>> type(17)\n<class 'int'><\/code><\/pre>\n
Not surprisingly,strings belong to the type str<\/code> and integers belong to the type int<\/code>. Less obviously, numbers with a decimal point belong to a type called float<\/code>, because these numbers are represented in a format called floating point.<\/p>\n
>>> type(3.2)\n<class 'float'><\/code><\/pre>\n
What about values like "17" and "3.2"? They look like numbers, but they are in quotation marks like strings.<\/p>\n
>>> type('17')\n<class 'str'>\n>>> type('3.2')\n<class 'str'><\/code><\/pre>\n
They're strings.<\/p>\n
When you type a large integer, you might be tempted to use commas between groups of three digits, as in 1,000,000. This is not a legal integer in Python, but it is legal:<\/p>\n
>>> print(1,000,000)\n1 0 0<\/code><\/pre>\n
Well, that's not what we expected at all! Python interprets 1,000,000 as a comma-separated sequence of integers, which it prints with spaces between.<\/p>\n
This is the first example we have seen of a semantic error: the code runs without producing an error message, but it doesn't do the "right" thing.<\/p>\n
Variables<\/h3>\n
One of the most powerful feature of a programming language is the ability to manipulate variable. A variable is a name refers to a value.<\/p>\n
An assignment statement creates new variables and gives them values:<\/p>\n
>>> message = 'And now for something completely different'\n>>> n = 17\n>>> pi = 3.1415926535897931<\/code><\/pre>\n
This example makes three assighments. The first assighs a string a new varialbe named message<\/code>; the second assighs the integer 17 to n<\/code>; the third assighs the(approximate)value of \u03c0 to pi<\/code>.<\/p>\n
To display the vlaue of a variable, you can use a print statement:<\/p>\n
>>> print(n)\n17\n>>> print(pi)\n3.141592653589793<\/code><\/pre>\n
The type of a variable is the type of the value it refers to.<\/p>\n
>>> type(message)\n<class 'str'>\n>>> type(n)\n<class 'int'>\n>>> type(pi)\n<class 'float'><\/code><\/pre>\n
Variable names and keywords<\/h3>\n
Programmers generally choose names of their variables that are meaningful and document what the variable is used for.<\/p>\n
variable names can be arbitrarily long. They can contain both letters and numbers, but they cannot start with a number. It is legal to use uppercase letters, but it is a good idea to begin variable names with a lowercase letter(you'll see why later).<\/p>\n
The underscore charater(_) can appear in a name. It is often used in names with multiple words, such as my_name<\/code> or airspeed_of_unladen_swallow<\/code>.
\nVariable names can start with an underscore charater, but we generally aviod doing this unless we are writing library code for others to use.<\/p>\n
If you give a variable an illegal name, you get a syntax error:<\/p>\n
>>> 76trombones = 'big parade'\nSyntaxError: invalid syntax\n>>> more@ = 1000000\nSyntaxError: invalid syntax\n>>> class = 'Advanced Theoretical Zymurgy'\nSyntaxError: invalid syntax<\/code><\/pre>\n
76trombones<\/code> is illegal because it begings with a number.
\nmore@<\/code> is illegal because it contains an illegal charater, @. But what's wrong with class<\/code>?<\/p>\n
It turns out that class<\/code> is one of Python's keywords. The interpreter uses keywords to recognize the structure of the program, and they cannot be used as variable names.<\/p>\n
Python reserves 35 keywords:<\/p>\n
False      await      else       import     pass\nNone       break      except     in         raise\nTrue       class      finally    is         return\nand        continue   for        lambda     try\nas         def        from       nonlocal   while\nassert     del        global     not        with\nasync      elif       if         or         yield<\/code><\/pre>\n
You might want to keep this list handy. If the interpreter complains about one of your variable names and you don't know why, see if it is on this list.<\/p>\n
Statements<\/h3>\n
A statement is a unit of code that the Python interpreter can execute. We have seen two kinds of staements: print being an expression assignment.<\/p>\n
When you type a statement in interactive mode, the interpreter executes it and displays the result, if there is one.<\/p>\n
A script usually contains a sequence of statement. If there is more than one statement, the rusults appear one at a time as the statements execute.<\/p>\n
For example, the script<\/p>\n
print(1)\nx = 2\nprint(x)<\/code><\/pre>\n
produces the output<\/p>\n
1\n2<\/code><\/pre>\n
The assignment statement produces no output.<\/p>\n
Operators and operands<\/h3>\n
Operators are special symbols that represent computations like addition and multiplication. The values the operator is apllied to are called operands.<\/p>\n
The operators +<\/code> -<\/code> *<\/code> \/<\/code>, and **<\/code> perform addition, subtraction, multiplication, division, and exponential\uff0c as in the following example:<\/p>\n
20+32\nhour-1\nhour*60+minute\nminute\/60\n5**2\n(5+9)*(15-7)<\/code><\/pre>\n
There has been a change in the division operator between Python 2 and Python 3. In Python3, the result of this division is a floating point result:<\/p>\n
>>> minute = 59\n>>> minute\/60\n0.9833333333333333<\/code><\/pre>\n
The division operator in Python 2 would divide two integers and truncate the result to an integer:<\/p>\n
>>> minute = 59\n>>> minute\/60\n0<\/code><\/pre>\n
To obtain the same answer in Python 3 use floored(\/\/<\/code> integer) division.<\/p>\n
>>> minute = 59\n>>> minute\/\/60\n0<\/code><\/pre>\n
In python 3 integer division functions much more as you would expect if you entered the expression on a calculation.<\/p>\n
Expressions<\/h3>\n
An expression is a combination of values, variable, and operators.
\nA value all by itself is considered an expression, and so is a variable, so the following are all legal expression(assuming that the variable x<\/code> has been assigned a value)<\/p>\n
17\nx\nx + 17<\/code><\/pre>\n
If you type an expression in interactive mode, the interpreter evaluates it and displays the result:<\/p>\n
>>> 1+1\n2<\/code><\/pre>\n
But in a script, an expression all by itself doesn't do anything! This is common source of confusion for beginners.<\/p>\n
Exercise 1:<\/strong> Type the following statements in the Python interpreter to see what they do:<\/p>\n
5\nx = 5\nx + 1<\/code><\/pre>\n
Order of operations<\/h3>\n
When more than one operator appears in an expression, the order of evaluation depends on the rules of precedence.
\nFor mathematical operators, Python follows mathematical convention.
\nThe acronym PEMDA is a useful way to remenber the rules:<\/p>\n
    \n
  • \n
    Parentheses have the highest precedence and can be used to force an expression to evaluate in the order you want. Since expressions in parentheses are evaluate first, 2 * (3-1)<\/code> is 4, and (1+1)**(5-2)<\/code> is 8. You can also use parentheses to make an expression easier to read, as in (minute * 100) \/ 60<\/code>, even if it doesn't change the result.<\/p>\n<\/li>\n
  • \n
    Exponential has the next highest precedence, so 2**1+1<\/code> is 3, not 4, 3*1**3<\/code> is 3, not 27.<\/p>\n<\/li>\n
  • \n
    Multiplication and division have the same precedence, which is higher than Addition and Subtraction, which also have the same precedence. So 2*3-1<\/code> is 5, not 4, and 6+4\/2<\/code> is 8, not 5.<\/p>\n<\/li>\n
  • \n
    Operators with the same precedence are evaluated from left to right. So the expression 5-3-1<\/code> is 1, not 3, because the 5-3<\/code> happens first and then 1<\/code> is subtracted from 2.<\/p>\n<\/li>\n<\/ul>\n
    When in doubt, always put parentheses in your expressions to make sure the computations are performed in the order you intend.<\/p>\n
    Modulus operator<\/h3>\n
    The modulus operator works on integers and yields the remainder when the first operand is divided by the second. In Pyton, the modulus operator is a percent sign(%<\/code>). The syntax is the same as for other operators:<\/p>\n
    >>> quotient = 7 \/\/ 3\n>>> print(quotient)\n2\n>>> remainder = 7 % 3\n>>> print(remainder)\n1<\/code><\/pre>\n
    So 7 divided by 3 is 2 with 1 left over.<\/p>\n
    The modulus operator turns out t be surprisingly useful. For example, you can check whether one number is divisible by another: if x % y<\/code> is zero, then x<\/code> is divisible by y<\/code>.<\/p>\n
    You can also extract the right-most digit or digits from a number.
    \nFor example, x % 10<\/code> yields the right-most digit of x<\/code> (in base 10).
    \nSimilarly, x % 100<\/code> yields the last two digits.<\/p>\n
    String operations<\/h3>\n
    The +<\/code> operator works with strings, but it is not addition in the mathematical sense.
    \nInstead it performs concatenation, which means joining the string by linking them end to end.
    \nFor example:<\/p>\n
    >>> first = 10\n>>> second = 15\n>>> print(first+second)\n25\n>>> first = '100'\n>>> second = '150'\n>>> print(first + second)\n100150<\/code><\/pre>\n
    The *<\/code> operator also works with strings by multiplying the content of a string by an integer.
    \nFor example:<\/p>\n
    >>> first = 'Test '\n>>> second = 3\n>>> print(first * second)\nTest Test Test<\/code><\/pre>\n
    Asking the user for input<\/h3>\n
    Sometimes we would like to take a value for a variable from the user via their keyboard.
    \nPython provides a built-in function called input<\/code> that gets input from the keyboard.
    \nWhen this function is called, the program stops and waits for the user to type something.
    \nWhen the user presses Return<\/code> or Enter<\/code>, the program resumes and input<\/code> returns what user typed as a string.<\/p>\n
    >>> inp = input()\nSome silly stuff\n>>> print(inp)\nSome silly stuff<\/code><\/pre>\n
    Befor getting input from the user, it is a good idea to print a prompt telling the user what to input.
    \nYou can pass a string to input<\/code> to be displayed to the user before pausing for input:<\/p>\n
    >>> name = input('What is your name?\\n')\nWhat is your name?\nChuck\n>>> print(name)\nChuck<\/code><\/pre>\n
    The senquence \\n<\/code> at the end of the prompt represents a newline, which is a special charater that cause a line break.
    \nThat's why the user's input appears below the prompt.<\/p>\n
    If you expect the user to type an integer, you can try to convert the return value to int<\/code> using the int()<\/code> function:<\/p>\n
    >>> prompt = 'What...is the airspeed velocity of an unladen swallow?\\n'\n>>> speed = input(prompt)\nWhat...is the airspeed velocity of an unladen swallow?\n17\n>>> int(speed)\n17\n>>> int(speed) + 5\n22<\/code><\/pre>\n
    But if the user types something other than a string of digits, you get an error:<\/p>\n
    >>> speed = input(prompt)\nWhat...is the airspeed velocity of an unladen swallow?\nWhat do you mean, an African or a European swallow?\n>>> int(speed)\nValueError: invalid literal for int() with\nbase 10: 'What do you mean, an African or a European swallow?'<\/code><\/pre>\n
    We will see how to handle this kind of error later.<\/p>\n
    Comments<\/h3>\n
    As programs get bigger and more complicated, they get more difficult to read.
    \nFormal language are dense, and it is often difficult to look at a piece of code and figure out what it is doing, or why.<\/p>\n
    For this reason, it is a good idea to add notes to your programs to explain in natrual language what the program is dong. Thest notes are called comments, and in python they start with #<\/code> symbol:<\/p>\n
    # compute the percentage of the hour that has elapsed\npercentage = (minute * 100) \/ 60<\/code><\/pre>\n
    In this case, the comment appears on a line by itself. You can also put commands at the end of a line:<\/p>\n
    percentage = (minute * 100) \/ 60     # percentage of an hour<\/code><\/pre>\n
    Everything from the #<\/code> to the end of the line is ignored; it has no effect on the program.<\/p>\n
    Comments are most useful when they document non-abvious features of the code.
    \nIt is reasonable to assume that the reader can figure out what the code does; it is much more useful to explain why.<\/p>\n
    This comments is redundant with the code and useless:<\/p>\n
    v = 5   # assign 5 to v<\/code><\/pre>\n
    This comment contains useful information that is not in the code:<\/p>\n
    v = 5   # velocity in meters\/second<\/code><\/pre>\n
    Good variable names can reduce the need for comments, but long names can make complex expressions hart to read, so there is a trade-off.<\/p>\n
    Choosing mnemonic variable names<\/h3>\n
    As long as you follow the simple rules of variable naming, and avoid reserved words, you have a lot of choice when you name your variables. In the beginning, this choice can confusing both when you read a program and when you write your own programs. the following three programs are identical in terms of what they accomplish, but they different when you read them and try to understand them.<\/p>\n
    a = 35.0\nb = 12.50\nc = a * b\nprint(c)<\/code><\/pre>\n
    hours = 35.0\nrate = 12.50\npay = hours * rate\nprint(pay)<\/code><\/pre>\n
    x1q3z9ahd = 35.0\nx1q3z9afd = 12.50\nx1q3p9afd = x1q3z9ahd * x1q3z9afd\nprint(x1q3p9afd)<\/code><\/pre>\n
    The Python interpreter sees all three of these programs as exactly the same but humans see and understand these programs quite differently. Humans will most quickly understand the intent of the second program because the programer has chosen variable names that reflect their intent regarding what data will be stored in each variable.<\/p>\n
    We call these wisely chosen variable names "mnemonic variable names". The word mnemonic means "memory aid".
    \nWe choose mnemonic variable names to help us remember why we created the variable in the first place.<\/p>\n
    While this all sounds great, and it is a very good idea to use mnemonic variable names, mnemonic variable names can get in the way of a beginning programmer's ability to parse and understand code. This is because beginning programmers have not yet memorized the reserved words (there are only 35 of them) and sometimes variable with names that are too descriptive start to look like part of the language and not just well-chosen variable names.<\/p>\n
    Take a quick look at the following Python sample code which loops through some data. We will cover loop soon, but for now try to puzzle through what this means:<\/p>\n
    for word in words:\n    print(word)<\/code><\/pre>\n
    What is happening here? Which of the tokens (for,word,in,etc.) are reserved words and wich are just variable name? Does Python understand at a fundamental level the notion of words? Beginning programmers have trouble separating what parts of the code must be the same as this example and what parts of the code are simply choices made by programmer.<\/p>\n
    The following code is equivalent to the above code:<\/p>\n
    for slice in pizza:\n    print(slice)<\/code><\/pre>\n
    It is easier for the beginner programmer to look at this code and know which parts are reserved words defined by Python and which parts are simply variable names chosen by the programmer. It is pretty clear that Python has no fundamental understanding of pizza and slices and the fact that a pizza consists of a set of one or more slices.<\/p>\n
    But if our program is truly about reading data and looking for words in the data, pizza<\/code> and slice<\/code> are very unmnemonic variable names. Choosing them as variable names distracts from the meaning of the program.<\/p>\n
    After a pretty short period of time, you will know the most common reserved words and you will start to see the reserved words jumping out at you:<\/p>\n
    for word in words:\n    print(word)<\/code><\/pre>\n
    The parts of the code that are defined by Python (for<\/code>,in<\/code>,print<\/code>,and :<\/code>) are in bold and the programmer-chosen variable(word<\/code> and words<\/code>) are not in bold. Many text editors are aware of Python syntax and will color reserved words differently to give you clues to keep your variables and reversed words separate. After a while you will begin to read Python and quickly determine what is a variable and what is a reserved word.<\/p>\n
    Debugging<\/h3>\n
    At this point, the syntax error you are most likely to make is an illegal variable name, like class<\/code> and yield<\/code>, which are keywords, or odd~job<\/code> and US$<\/code>, wich contain illegal charaters.<\/p>\n
    If you put a space in a variable name, Python thinks it is two operands without an operator:<\/p>\n
    >>> bad name = 5\nSyntaxError: invalid syntax<\/code><\/pre>\n
    For syntax error, the error messages don't help much. The most common message are SyntaxError: invalid syntax<\/code> which is not very informative.<\/p>\n
    The runtime error you are most likely to make is a "use befor def;" that is, trying to use a variable before you have assigned a value. This can happen if you spell a variable name wrong:<\/p>\n
    >>> principal = 327.68\n>>> interest = principle * rate\nNameError: name 'principle' is not defined<\/code><\/pre>\n
    Variable names are case sensitive, so LaTex<\/code> is not the name as latex<\/code>.<\/p>\n
    At this point, the most likely cause of a semantic error is the order of operations.
    \nFor example, to evaluate 1\/2\u03c0, you might be tempted to write<\/p>\n
    >>> 1.0 \/ 2.0 * pi<\/code><\/pre>\n
    But the division happens first, so you would get \u03c0\/2, which is not the same thing!
    \nThere is no way for Python to know what you meant to write, so in this case you don't get an error message; you just get the wrong answer.<\/p>\n
    Glossary<\/h3>\n
    assignment<\/strong>
    \nA statement that assign a value to a variable.<\/p>\n
    concatenate<\/strong>
    \nTo join two operands end to end.<\/p>\n
    comment<\/strong>
    \nInformation in a program that is for other programmer (or anyone reading the souce code) and has no effect on the execution of the program.<\/p>\n
    evaluate<\/strong>
    \nTo simplify an expression by performing the operations in order to yield a single value.<\/p>\n
    expression<\/strong>
    \na combination of variables, operators, and values that represents a single result value.<\/p>\n
    floating point<\/strong>
    \nA type that represents numbers with fractional parts.<\/p>\n
    integer<\/strong>
    \nA type that represents whole numbers.<\/p>\n
    keyword<\/strong>
    \nA reserved word that is used by the compiler to parse a program; you cannot use keyword like if<\/code>, def<\/code>, and while<\/code> as variable names.<\/p>\n
    mnemonic<\/strong>
    \nA memory aid. We often give variables mnemonic names to help us remember what is stored in the variable.<\/p>\n
    modulus operator<\/strong>
    \nAn operator, denoted with a percent sign (%), that works integers and yields the remainder when one number is divided by another.<\/p>\n
    operands<\/strong>
    \nOne of the values on which an operator operates.<\/p>\n
    operator<\/strong>
    \nA special symbol that represents a simple comutation like addition, multiplication, or string concatenation.<\/p>\n
    rules of precedence<\/strong>
    \nThe set of rules governing the order in which expression involving multiple operators and operands are evaluated.<\/p>\n
    statement<\/strong>
    \nA section of code that represents a command or action. So far,the statements we have seen are assignments and print expression statement.<\/p>\n
    string<\/strong>
    \nA type that represents sequences of charaters.<\/p>\n
    type<\/strong>
    \nA category of values. The types we have seen so far are integer(type int<\/code>), floating-point numbers(type float<\/code>), and string(type str<\/code>)<\/p>\n
    value<\/strong>
    \nOne of the basic units of data, like a number or string, that a program manipulates.<\/p>\n
    variable<\/strong>
    \nA name that refers to a value.<\/p>\n
    Exercises<\/h3>\n
    Exercise 2:<\/strong> Write a program that uses input<\/code> to prompt a user for their name and then welcomes them.<\/p>\n
    Enter your name: Chuck\nHello Chuck<\/code><\/pre>\n
    inp = input('Enter your name: ')\nprint('Hello', inp)<\/code><\/pre>\n
    Exercise 3:<\/strong> Write a program to prompt the user for hours and rate per hour to compute gross pay.<\/p>\n
    Enter Hours: 35\nEnter Rate: 2.75\nPay: 96.25<\/code><\/pre>\n
    hours = float(input('Enter Hours: '))\nrate = float(input('Enter Rate: '))\nprint('Pay: ', hours * rate)<\/code><\/pre>\n
    We won't worry about making sure our pay has exactly two digits after the decimal place for now. If you want, you can play with the built-in Python round<\/code> function to properly round the resulting pay to two decimal places.<\/p>\n
    # \u83b7\u53d6\u7528\u6237\u8f93\u5165\u5e76\u8f6c\u6362\u4e3a\u6570\u503c\nhours = float(input("\u8bf7\u8f93\u5165\u5de5\u4f5c\u65f6\u957f\uff1a"))\nrate = float(input("\u8bf7\u8f93\u5165\u65f6\u85aa\uff1a"))\n\n# \u8ba1\u7b97\u603b\u5de5\u8d44\u5e76\u56db\u820d\u4e94\u5165\u5230\u4e24\u4f4d\u5c0f\u6570\ngross_pay = round(hours * rate, 2)\n\n# \u8f93\u51fa\u7ed3\u679c\nprint("\u603b\u5de5\u8d44\u4e3a\uff1a", gross_pay)<\/code><\/pre>\n
    Exercise 4:<\/strong> Assume that we execute the following assignment statements:<\/p>\n
    width = 17\nheight = 12.0<\/code><\/pre>\n
    For each of the following expressions, write the value of the expression and the type (of the value of the expression).<\/p>\n
      \n
    1. width\/\/2<\/code>  8  int<\/li>\n
    2. width\/2.0<\/code>  8.5  float<\/li>\n
    3. height\/3<\/code>  4.0  float<\/li>\n
    4. 1 + 2 * 5<\/code>  11  int<\/li>\n<\/ol>\n
      Exercise 5:<\/strong> Write a program which prompts the user for a Celsius temperature, convert the temperature to Fahrenheit, and print out the converted temperature.<\/p>\n
      inp = input('Enter Celsius Temperature: ')\ncel = float(inp)\nfahr = (cel * 9.0) \/ 5.0 + 32.0\nprint(fahr)<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"
      Variables, expressions, and statements values and types… » \u9605\u8bfb\u5168\u6587<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[24],"tags":[],"class_list":["post-2419","post","type-post","status-publish","format-standard","hentry","category-python"],"_links":{"self":[{"href":"http:\/\/blue.yn.cn\/index.php?rest_route=\/wp\/v2\/posts\/2419","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/blue.yn.cn\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blue.yn.cn\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blue.yn.cn\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/blue.yn.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2419"}],"version-history":[{"count":15,"href":"http:\/\/blue.yn.cn\/index.php?rest_route=\/wp\/v2\/posts\/2419\/revisions"}],"predecessor-version":[{"id":2608,"href":"http:\/\/blue.yn.cn\/index.php?rest_route=\/wp\/v2\/posts\/2419\/revisions\/2608"}],"wp:attachment":[{"href":"http:\/\/blue.yn.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2419"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blue.yn.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2419"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blue.yn.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2419"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}