Statements (34)
| Predicate | Object |
|---|---|
| gptkbp:instanceOf |
Python Enhancement Proposal
|
| gptkbp:author |
gptkb:Tim_Peters
|
| gptkbp:category |
gptkb:philosophy
|
| gptkbp:contentType |
The Zen of Python, by Tim Peters, is a collection of guiding principles for writing computer programs in Python.
|
| gptkbp:created |
2004-08-19
|
| https://www.w3.org/2000/01/rdf-schema#label |
PEP 20
|
| gptkbp:influenced |
Python programming style
|
| gptkbp:language |
English
|
| gptkbp:numberOfRooms |
19
|
| gptkbp:principle |
Although that way may not be obvious at first unless you're Dutch.
Although never is often better than *right* now. Although practicality beats purity. Beautiful is better than ugly. Complex is better than complicated. Errors should never pass silently. Explicit is better than implicit. Flat is better than nested. Now is better than never. Readability counts. Simple is better than complex. Sparse is better than dense. Unless explicitly silenced. Namespaces are one honking great idea -- let's do more of those! If the implementation is hard to explain, it's a bad idea. In the face of ambiguity, refuse the temptation to guess. If the implementation is easy to explain, it may be a good idea. Special cases aren't special enough to break the rules. There should be one-- and preferably only one --obvious way to do it. |
| gptkbp:pythonVersion |
All
|
| gptkbp:status |
Active
|
| gptkbp:title |
gptkb:The_Zen_of_Python
|
| gptkbp:url |
https://peps.python.org/pep-0020/
|
| gptkbp:bfsParent |
gptkb:Python
|
| gptkbp:bfsLayer |
5
|