The translation and interpretation of the Zen of Python

the Zen of Python, by Tim Peters Beautiful is better than ugly.Explicit is better than implicit.Simple is better than complex.Complex is better than complicated.Flat is better than nested.Sparse is better than dense.readability counts.Special cases aren ' t special enough to break the rules.Although practicality beats purity.Errors should never pass silently.unless explicitly silenced.in the face of ambiguity, refuse the temptation to guess.there should is one--and preferably only one--obvious the-do it.Although that is obvious at first unless you ' re Dutch.Now is better than never.Although never is often better than *right* now.If The implementation is hard to explain, it's a bad idea.If The implementation is easy to explain, it could be a good idea.namespaces is one honking great idea – let's do more than those!

The Zen of Python by Tim Peters beauty is better than ugliness (Python aims to write graceful code)clarity is better than obscure (graceful code should be clear, naming specification, style similar)simplicity is better than complexity (graceful code should be concise, not complex internal implementations)complexity is better than clutter (if complexity is unavoidable, there is no hard-to-understand relationship between the code, keep the interface simple)flattening is better than nesting (graceful code should be flat, not too much nesting)The interval is better than the compact (graceful code has the appropriate interval, do not expect a line of code to solve the problem)readability is important (graceful code is readable)even in the name of the practicality of the special case, the rules must not be violated (these rules are paramount) do not tolerate all errors unless you are sure you need to (catch exceptions accurately, do not write Except:pass-style code) when there are many possibilities, don't try to guessinstead, try to find one, preferably the only obvious solution (if unsure, use the brute-lifting method)Although this is not easy, because you are not the father of Python (here Dutch refers to Guido) It may be better not to do it , but it's better not to do it without thinking about it (before you do it) If you can't describe your plan to someone, it's certainly not a good plan; and vice versa (Program evaluation criteria) namespaces are a great idea and we should use them (advocacy and calling).

The translation and interpretation of the Zen of Python