来自c#背景,变量和方法名的命名约定通常是camelCase或PascalCase:
// C# example
string thisIsMyVariable = "a"
public void ThisIsMyMethod()
在Python中,我见过上面的情况,但我也见过使用下划线:
# python example
this_is_my_variable = 'a'
def this_is_my_function():
Python是否有更可取、更明确的编码风格?
来自c#背景,变量和方法名的命名约定通常是camelCase或PascalCase:
// C# example
string thisIsMyVariable = "a"
public void ThisIsMyMethod()
在Python中,我见过上面的情况,但我也见过使用下划线:
# python example
this_is_my_variable = 'a'
def this_is_my_function():
Python是否有更可取、更明确的编码风格?
当前回答
There is PEP 8, as other answers show, but PEP 8 is only the styleguide for the standard library, and it's only taken as gospel therein. One of the most frequent deviations of PEP 8 for other pieces of code is the variable naming, specifically for methods. There is no single predominate style, although considering the volume of code that uses mixedCase, if one were to make a strict census one would probably end up with a version of PEP 8 with mixedCase. There is little other deviation from PEP 8 that is quite as common.
其他回答
David Goodger(在这里的“像Pythonista一样编码”中)描述了PEP 8的建议如下:
Joined_lower函数,方法, 属性、变量 joined_lower或ALL_CAPS for 常量 课程用的studlycap 骆驼案只符合 已有的约定
列宁告诉过……我也是来自Java/ c#世界的。还有SQL。 仔细审视我自己,试图找到第一眼就能理解的复杂结构的例子,比如列表字典中的列表,其中所有东西都是对象。 对我来说,骆驼语或它们的变体应该成为任何语言的标准。在复杂句中应保留下划线。
谷歌Python风格指南有以下约定:
module_name, package_name, ClassName, method_name, ExceptionName, function_name, GLOBAL_CONSTANT_NAME, global_var_name, instance_var_name, function_parameter_name, local_var_name。
CLASS_CONSTANT_NAME应该应用类似的命名方案
就我个人而言,我尝试在类、mixedCase方法和函数中使用CamelCase。变量通常用下划线分隔(当我记得的时候)。这样我一眼就能知道我到底在调用什么,而不是所有东西看起来都一样。
无论是否在课堂上或在课堂外:
变量和函数小写,如下所示:
name = "John"
def display(name):
print("John")
如果它们多于一个单词,则用下划线“_”分隔,如下所示:
first_name = "John"
def display_first_name(first_name):
print(first_name)
并且,如果一个变量是一个常量,它是大写的,如下所示:
FIRST_NAME = "John"