Shulou(Shulou.com)06/01 Report--

This article mainly explains "what is the meaning of Python Zen". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what is the meaning of Python Zen".

Q: what do you know about the Zen of Python?

Answer: the Zen of Python refers to the programming guidelines for python written by Tim Peters. We can enter: import this in the interactive interpreter. The Zen of Python, by Tim Peters will be displayed. The details are as follows:

> import this # enter import thisThe Zen of Python, by Tim PetersBeautiful 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 be one-- and preferably only one-- obvious way to do it.Although that way may not be 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 may be a good idea.Namespaces are one honking great idea-let's do more of those!

The above is translated into Chinese:

Python Zen by Tim Peters is more beautiful than ugly (Python aims to write beautiful code) is better than obscure (beautiful code should be clear, naming convention, similar style) simplicity is better than complex (beautiful code should be simple, without complex internal implementation) complex is better than messy (if complexity is inevitable, there can be no obscure relationship between code. To keep the interface simple) flat is better than nesting (beautiful code should be flat, not too much nesting) spacing is better than compact (beautiful code is properly spaced, don't expect a line of code to solve the problem) readability is important (beautiful code is readable) even under the guise of the usefulness of special cases, do not violate these rules (these rules are paramount) do not contain all errors Unless you're sure you need to do this (catch exceptions accurately, don't write except:pass-style code) when there are multiple possibilities, don't try to guess but try to find one, preferably the only obvious solution (if you're not sure, use exhaustion) although it's not easy, because you're not the father of Python (Dutch here means Guido) maybe it's better than not doing it. But doing it without thinking is better than not doing it (think carefully before doing it) if you can't describe your plan to others, it's definitely not a good plan. And vice versa (scheme evaluation criteria) Namespace is a wonderful idea, and we should make more use of it (advocacy and call)

Thank you for your reading. the above is the content of "what is the meaning of Python Zen". After the study of this article, I believe you have a deeper understanding of the meaning of Python Zen, and the specific use needs to be verified by practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.