Sign up to save your podcasts
Or
Share Episode 002: The Zen of Python, part 1
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
Episode 002: The Zen of Python, part 1
This is the first of two episodes where we’re going to explore PEP 20, that is,
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!
Real show notes to follow. With links and everything.
Podcast:
MP3
OGG
View all episodes
By Mike Pirnat, David Noyes, Benjamin W. Smith, David Stanek, Mike Crute, Chris MillerThis is the first of two episodes where we’re going to explore PEP 20, that is,
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!
Real show notes to follow. With links and everything.
Podcast:
MP3
OGG