Python编程从入门到实践-动动手课后习题（第二章）

Python小习题答案，本节题目为Python编程从入门到实践-动动手课后习题。

# 2.1 将一条消息存储到变量中，再将其打印出来。
a = 'World'
print(a)

"""
输出结果：
World

"""

# 2.2 多条简单消息：将一条消息存储到变量中，将其打印出来；
#     再将变量值修改为一条消息，并将其打印出来。

a = 'world'
print(a)

a = 'holle world'
print(a)

"""
输出结果：
world
holle world

"""

# 2.3 个性化消息：将用户的名字存储到一个变量中，并向该用户显示一条消息。
name = 'World'
print('Holle,' + name + '.')

"""
输出结果：
Holle,World.

"""

# 调整名字大小写：写一个人名到变量中，再以小写、大写和首字母显示人名。
name = 'tom'
print(name.lower())
print(name.upper())
print(name.title())

"""
输出结果：
tom
TOM
Tom
"""

# 2.5 名言
print('Albert Einstein once said, “A person who never made a mistake never tried anything new.”')


"""
输出结果：
Albert Einstein once said, “A person who never made a mistake never tried anything new.”
"""

# 2.6 名言2
name = 'Albert Einstein'
word = 'A person who never made a mistake never tried anything new.'

print(name + ' once said,' + '"' + word + '"')

"""
输出结果：
Albert Einstein once said,"A person who never made a mistake never tried anything new."
"""

# 2.7 剔除空白字符
name = "\n  TOM\t"
print(name)
print(name.lstrip())
print(name.rstrip())
print(name.strip())

"""
输出结果：

  TOM	
TOM	

  TOM
TOM

"""

# 2.8 数字8
print(1 + 7)
print(10 - 2)
print(2 * 4)
print(8 / 1)


"""
输出结果：
8
8
8
8.0
"""

# 2.9 最喜欢的数字
my_favorite_number = 7
print(str(my_favorite_number))

"""
输出结果：
7
"""

# 用#单行注释，用"""  """多行注释

# 2.11 python之禅

import this

"""
输出结果：
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!

"""