#zen of python

[python-programming-language]

Post #106: Python.Hub on Instagram, The different operators in Python, 2023.

[python-programming-language]

The philosophy of Python

The Zen of Python is a collection of 19 "guiding principles" for writing computer programs that influence the design of the Python programming language. Software engineer Tim Peters wrote these principles and posted them on the Python mailing list in 1999. Peters' list left open a 20th principle "that Guido must fill in," referring to Guido van Rossum, the original author of the Python language. The vacancy for a 20th principle has not been filled. (www.wikipedia.com)

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.

Although that way may not be obvious at first unless you're Dutch. LOL

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!

Die Philosophie von Python

Das Zen von Python ist eine Sammlung von 19 "Leitprinzipien" für das Schreiben von Computerprogrammen, die das Design der Programmiersprache Python beeinflussen. Der Software-Entwickler Tim Peters schrieb diese Prinzipien auf und veröffentlichte sie 1999 auf der Python-Mailingliste. Peters' Liste ließ ein 20. Prinzip offen, das "Guido" ausfüllen muss, und bezog sich dabei auf Guido van Rossum, den ursprünglichen Autor der Python-Sprache. Die Vakanz für ein 20. Prinzip wurde nicht besetzt. (www.wikipedia.com)

Schön ist besser als hässlich.

Explizit ist besser als implizit.

Einfach ist besser als kompliziert.

Komplex ist besser als undurchschaubar.

Flach ist besser als verschachtelt.

Spärlich ist besser als beschränkt.

Lesbarkeit zählt.

Spezialfälle sind nicht speziell genug, als dass sie die Regeln sprengen dürften.

Obwohl die praktische Anwendbarkeit die Reinheit übertrifft.

Fehler sollten nie schweigend verlaufen.

Außer man hat sie explizit zum Schweigen gebracht.

Im Angesicht der Mehrdeutigkeit widerstehe der Versuchung zu raten.

Es sollte einen --- und bevorzugt genau einen --- offensichtlichen Weg geben, es zu tun.

Obwohl dieser Weg auf den ersten Blick nicht offensichtlich erscheinen mag, außer man ist Holländer. LOL

Jetzt ist besser als nie. Obwohl nie oft besser ist als JETZT SOFORT.

Wenn die Implementierung schwer zu erklären ist, ist es eine schlechte Idee.

Wenn die Implementierung einfach zu erklären ist, könnte es eine gute Idee sein.

Namensräume sind eine glänzende Idee --- lasst uns mehr davon machen!

Post: #34: Tim Peters, The Zen Of Python, 1999.

[ozarde]

Python Creators Value Design

Python Creators Value Design

Guido van Rossum is a Dutch programmer best known as the author of the Python programming language. Python was created at the end of 1980s. Its implementation started in 1989. Python’s philosophy is very interesting as it includes several aphorisms.

Python is now becoming one of the most popular programming languages in the world. Python is quickly becoming the top choice among developers for 

View On WordPress

[winnydejong]

The Zen of Python

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. 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 Zen of Python () is a collection of 20 software principles that influences the design of Python Programming Language, written down around June 1999 by longtime Pythoneer Tim Peters. (Origin | Meaning)

[lunacodes]

Explicit is better than Implicit

[lunacodes]

In the face of ambiguity, refuse the temptation to guess

-The Zen of Python

[lunacodes]

"The koans are a group of little sayings about how to write good code. There’s an Easter egg (that is, a little hidden surprise) in the Python interactive shell where if you try to import a module named this, then it will display ―The Zen of Python‖ koans."

>>> import this 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 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!

[sydneyapprentice]

Zen of Python

"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. 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!" Tim Peters, via Thinkful