Style Guide for Python Code Programmers blog（Python代码的程序员的博客风格指南）.pdfVIP

Style Guide for Python Code Introduction This document gives coding conventions for the Python code comprising the standard library in the main Python distribution. Please see the companion informational PEP describing style guidelines for the C code in the C implementation of Python [1]. This document and PEP 257 (Docstring Conventions) were adapted from Guidos original Python Style Guide essay, with some additions from Barrys style guide [2]. This style guide evolves over time as additional conventions are identified and past conventions are rendered obsolete by changes in the language itself. Many projects have their own coding style guidelines. In the event of any conflicts, such project- specific guides take precedence for that project. A Foolish Consistency is the Hobgoblin of Little Minds One of Guidos key insights is that code is read much more often than it is written. The guidelines provided here are intended to improve the readability of code and make it consistent across the wide spectrum of Python code. As PEP 20 says, Readability counts. A style guide is about consistency. Consistency with this style guide is important. Consistency within a project is more important. Consistency within one module or function is most important. But most importantly: know when to be inconsistent -- sometimes the style guide just doesnt apply. When in doubt, use your best judgment. Look at other examples and decide what looks best. And dont hesitate to ask! In particular: do not break backwards compatibility just to comply with this PEP! Some other good reasons to ignore a particular guideline: When applying the guideline would make the code less readable, even for someone who is used to reading code that follows this PEP. To be consistent with surrounding code that also breaks it (maybe for historic reasons) -- although this is also an opportunity to clean up someone elses mess (i