擅长:python、mysql、java
<p>为了保持一致,您可以使用<em>under \u scores</em>而不是<em>camelCase</em>,因为前者比后者更具可读性。您可以看到一篇关于命名约定<a href="https://softwareengineering.stackexchange.com/a/27293">here</a>的文章。你知道吗</p>
<p><em>在某些情况下使用这两种方法是否都是可以接受的?</em></p>
<p>是的,这是可以接受的和Python都使用,但只有在某些情况下。您可以检查devs的<a href="https://www.python.org/dev/peps/pep-0008/" rel="nofollow noreferrer">PEP-8</a>guid。你知道吗</p>
<p>函数名</p>
<blockquote>
<p>Function names should be lowercase, with words separated by underscores as necessary to improve readability.</p>
</blockquote>
<p>某些情况包括向后兼容性</p>
<blockquote>
<p>mixedCase is allowed only in contexts where that's already the prevailing style (e.g. threading.py), to retain backwards compatibility.</p>
</blockquote>
<p>对于类名</p>
<blockquote>
<p>Class names should normally use the CapWords convention.</p>
<p>The naming convention for functions may be used instead in cases where the interface is documented and used primarily as a callable.</p>
</blockquote>
<p>最后,如果你是建立在一些图书馆的顶部,最好是与图书馆的风格。对于pythonic约定,<a href="https://www.python.org/dev/peps/pep-0008/" rel="nofollow noreferrer">PEP-8</a>用于指导开发人员。你知道吗</p>