Statements (28)
| Predicate | Object |
|---|---|
| gptkbp:instance_of |
gptkb:philosophy
|
| gptkbp:advocates_for |
explicitness
|
| gptkbp:author |
gptkb:Tim_Peters
|
| gptkbp:contains |
gptkb:guidelines
|
| gptkbp:emphasizes |
readability
|
| https://www.w3.org/2000/01/rdf-schema#label |
Zen of Python
|
| gptkbp:influences |
Python design decisions
|
| gptkbp:is |
a collection of aphorisms
|
| gptkbp:is_accessible_by |
import this
|
| gptkbp:is_cited_in |
Python developers
|
| gptkbp:is_considered |
a guiding principle
|
| gptkbp:is_part_of |
Python's culture
|
| gptkbp:is_recommended_by |
there should be one—and preferably only one—obvious way to do it.
|
| gptkbp:is_related_to |
gptkb:PEP_20
|
| gptkbp:is_used_in |
Python programming community
|
| gptkbp:language |
gptkb:Python
|
| gptkbp:promotes |
simplicity
|
| gptkbp:state |
if the implementation is easy to explain, it may be a good idea.
if the implementation is hard to explain, it's a bad idea. complex is better than complicated. there should be one—and preferably only one—obvious way to do it. readability counts. simple is better than complex. namespaces are one honking great idea—let's do more of those! in the face of ambiguity, refuse the temptation to guess. |
| gptkbp:written_in |
English
|
| gptkbp:bfsParent |
gptkb:Python
|
| gptkbp:bfsLayer |
4
|