Jump to content

Zen of Python

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Erictleung (talk | contribs) at 18:34, 7 February 2024 (Update reference metadata). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
The Zen of Python output in a terminal

The Zen of Python is a collection of 19 "guiding principles" for writing computer programs that influence the design of the Python programming language.[1]

Software engineer Tim Peters wrote this set of principles and posted it on the Python mailing list in 1999.[2] Peters's list left open a 20th principle "for Guido to fill in", referring to Guido van Rossum, the original author of the Python language. The vacancy for a 20th principle has not been filled.

Peters' Zen of Python was included as entry number 20 in the language's official Python Enhancement Proposals and was released into the public domain.[3] It is also included as an Easter egg in the Python interpreter, where it can be displayed by entering import this.[1][3][a]

In May 2020, Barry Warsaw (developer of GNU Mailman) wrote the lyrics to music.[5][6]

Principles

The Zen of Python illustrated

The principles are listed as follows:[b]

  • 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 be one-- and preferably only one --obvious way to do it.[c]
  • 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.[d]
  • 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!

Being Pythonic

One of the principles, "There should be one-- and preferably only one --obvious way to do it", can be referenced as the "Pythonic" way.[8] The official definition of "Pythonic" is:[9]

An idea or piece of code which closely follows the most common idioms of the Python language, rather than implementing code using concepts common to other languages. For example, a common idiom in Python is to loop over all elements of an iterable using a for statement. Many other languages don’t have this type of construct, so people unfamiliar with Python sometimes use a numerical counter instead: 

for i in range(len(food)):
    print(food[i])

As opposed to the cleaner, Pythonic method: 

for piece in food:
    print(piece)

In practice

Since the release of the Zen of Python, there has been research done on its effectiveness and actual use among developers. Despite the difference in interpretation between beginners and experienced Python programmers, interviews among 13 Python programmers of varying skill show that the Zen of Python "positively influences the way developers write and talk about code".[8]

See also

Notes

  1. ^ The source code for the Zen of Python is decidedly, and by design, un-Pythonic[4][citation needed] https://github.com/python/cpython/blob/main/Lib/this.py
  2. ^ Wikipedia links below are added for further reference and understanding, and were not explicitly linked in the Zen of Python
  3. ^ The formatting of the dashes in this line and the final is purposely inconsistent, in reference to the varying formatting conventions.[7]
  4. ^ In the interpreter easter egg, this is written as "Although never is often better than *right* now." This follows a longstanding convention of plain-text communication — in which common formatting features are often impossible — where emphasis is represented with asterisks.

References

  1. ^ a b Reitz, Kenneth (2011–2019). "Code Style". The Hitchhiker’s Guide to Python. § Zen of Python. Retrieved March 26, 2019.
  2. ^ Peters, Tim (June 4, 1999). "The Python Way". Python Software Foundation. Retrieved March 26, 2019.
  3. ^ a b Peters, Tim (August 19, 2004). "PEP 20—The Zen of Python". Python Software Foundation. Retrieved March 26, 2019.
  4. ^ https://stackoverflow.com/a/25011492/2468369
  5. ^ Warsaw, Barry (10 May 2020). "The Zen of Python". We Fear Change. Archived from the original on 2020-06-03.
  6. ^ Warsaw, Barry (23 May 2020). The Zen of Python. YouTube. The Zbwedicon. Archived from the original on 2021-12-11. Archived 2020-06-03 at the Wayback Machine
  7. ^ "Issue 3364: An ortographical typo in Zen of Python text - Python tracker". Retrieved 2021-02-10.
  8. ^ a b Alexandru, Carol V.; Merchante, José J.; Panichella, Sebastiano; Proksch, Sebastian; Gall, Harald C.; Robles, Gregorio (2018-10-24). "On the usage of pythonic idioms". Proceedings of the 2018 ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Software. Onward! 2018. New York, NY, USA: Association for Computing Machinery: 1–11. doi:10.1145/3276954.3276960. ISBN 978-1-4503-6031-9. Archived from the original on 2018-10-03 – via Association for Computing Machinery.
  9. ^ "Glossary". Python Documentation. Retrieved 2024-02-07.
Stub icon

This article about an essay or essay collection is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Zen_of_Python&oldid=1204684964"