@JohnTESlade的回答更进一步。谷歌的python风格指南有一些非常简洁的建议，

避免使用的名字

除计数器或迭代器外的单字符名称 在任何包/模块名称中使用破折号(-) \ __double_leading_and_trailing_下划线名称(由Python保留)

命名约定

"Internal" means internal to a module or protected or private within a class. Prepending a single underscore (_) has some support for protecting module variables and functions (not included with import * from). Prepending a double underscore (__) to an instance variable or method effectively serves to make the variable or method private to its class (using name mangling). Place related classes and top-level functions together in a module. Unlike Java, there is no need to limit yourself to one class per module. Use CapWords for class names, but lower_with_under.py for module names. Although there are many existing modules named CapWords.py, this is now discouraged because it's confusing when the module happens to be named after a class. ("wait -- did I write import StringIO or from StringIO import StringIO?")

指南源自圭多的建议

我个人在用其他编程语言开发时使用Java的命名约定，因为它是一致的，易于遵循。这样我就不会一直纠结于使用什么约定，而这本来不应该是我项目中最难的部分!

@JohnTESlade的回答更进一步。谷歌的python风格指南有一些非常简洁的建议，

避免使用的名字

除计数器或迭代器外的单字符名称 在任何包/模块名称中使用破折号(-) \ __double_leading_and_trailing_下划线名称(由Python保留)

命名约定

"Internal" means internal to a module or protected or private within a class. Prepending a single underscore (_) has some support for protecting module variables and functions (not included with import * from). Prepending a double underscore (__) to an instance variable or method effectively serves to make the variable or method private to its class (using name mangling). Place related classes and top-level functions together in a module. Unlike Java, there is no need to limit yourself to one class per module. Use CapWords for class names, but lower_with_under.py for module names. Although there are many existing modules named CapWords.py, this is now discouraged because it's confusing when the module happens to be named after a class. ("wait -- did I write import StringIO or from StringIO import StringIO?")

指南源自圭多的建议

参见Python PEP 8:函数和变量名:

函数名应该是小写的，单词之间用下划线分隔，以提高可读性。 变量名遵循与函数名相同的约定。 mixedCase只允许在已经是流行风格的上下文中使用(例如threading.py)，以保持向后兼容性。

有一篇关于这方面的论文:http://www.cs.kent.edu/~jmaletic/papers/ICPC2010-CamelCaseUnderScoreClouds.pdf

它说snake_case比camelCase可读性更好。这就是为什么现代语言在任何可能的地方都使用(或应该使用)蛇。

编码风格通常是组织内部策略/约定标准的一部分，但我认为一般来说，all_lower_case_underscore_separator风格(也称为snake_case)在python中最常见。