【Python開發web】(3) — Python基礎之一

開始靜下心來認真學習Python的基礎：The Python Tutorial

今天看了前面的一些章節，見：

 

-------------------------------------------我是pangpang分隔線------------------------------------------

 

值得關注的要點有：

1) 中文字元的長度

經測試，一個中文字元佔3個，見

 

-------------------------------------------我是pangpang分隔線------------------------------------------

 

2) 在一些語言中，“=”代表引用，在Python中是複製而非引用，見：

 

-------------------------------------------我是pangpang分隔線------------------------------------------

 

3) 在調用函數時，不按參數的順序，直接指定參數名和值也可以傳遞，見：

 

-------------------------------------------我是pangpang分隔線------------------------------------------

 

4) Python的代碼規範，直到看到這段文字後，我才將Tab改為了4-space，受教了。 

 

Now that you are about to write longer, more complex pieces of Python, it is a good time to talk about coding style. Most languages can be written (or more concise, formatted) in different styles; some are more readable than others. Making it easy for others to read your code is always a good idea, and adopting a nice coding style helps tremendously for that.

For Python, PEP 8 has emerged as the style guide that most projects adhere to; it promotes a very readable and eye-pleasing coding style. Every Python developer should read it at some point; here are the most important points extracted for you:

• Use 4-space indentation, and no tabs.

  4 spaces are a good compromise between small indentation (allows greater nesting depth) and large indentation (easier to read). Tabs introduce confusion, and are best left out.

• Wrap lines so that they don’t exceed 79 characters.

  This helps users with small displays and makes it possible to have several code files side-by-side on larger displays.

• Use blank lines to separate functions and classes, and larger blocks of code inside functions.

• When possible, put comments on a line of their own.

• Use docstrings.

• Use spaces around operators and after commas, but not directly inside bracketing constructs: a = f(1, 2) + g(3, 4).

• Name your classes and functions consistently; the convention is to use CamelCase for classes and lower_case_with_underscores for functions and methods. Always use self as the name for the first method argument (see A First Look at Classes for more on classes and methods).

• Don’t use fancy encodings if your code is meant to be used in international environments. Plain ASCII works best in any case.