Python, it speaks to me. Seriously.

Python, it speaks to me. Seriously.

Jan 13

I have some serious writers block this evening. It’s been a long, hard day, it’s late and I can’t think of anything to write about (or can’t think, period), so here’s some cool Python edutainmusement(tm):

The Zen Of Python, by Tim Peters

From the python command line:

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

Shooting yourself in the foot:

Python: You create a gun module, a gun class, a foot module and a foot class. After realising you can’t point the gun at the foot, you pass a reference to the gun to a foot object. After the foot is blown up, the gun object remains alive for eternity, ready to shoot all future feet that may happen to appear.
Java: You find that Microsoft and Sun have released imcompatible class libraries both implementing Gun objects. You then find that although there are plenty of feet objects implemented in the past in many other languages, you cannot get access to one. But seeing as Java is so cool, you dont care and go around shooting anything else you can find.
—Mark Hammond

TCL vs. Perl vs. Python

Subject: Re: Python vs Tcl vs Perl5
From: Andrew Dalke <>
Date: 24 Feb 1997 15:38:48 GMT

Ali Shah <> asked:
> if anyone out there has done some sort of evaluation about the
> suitability of [Python, Tcl or Perl5] for different applications?

Granted, the following has little to do with your questions... :)

Tcl -- It is short (only three letters) and does a suprising
amount given that it doesn't have a vowel.  It can be
pronounced "Tickle", which is a command.

Perl -- Bigger and has a vowel.  However you'll note that it isn't
a common english word; you'll have to know what you're doing to
use it, especially with spell-checkers which otherwise complain
that it looks like noise.

Python -- This is a Real English Word (honest, look it up!) that
happens to refer to a type of snake, which you'll notice is an
object.  With the two vowels, python is quite readable.

Use the force young Skywalker:

           With Yoda strapped to his back, Luke climbs up one of
        the many thick vines that grow in the swamp until he
        reaches the Dagobah statistics lab. Panting heavily, he
        continues his exercises -- grepping, installing new
        packages, logging in as root, and writing replacements for
        two-year-old shell scripts in Python.

YODA: Code!  Yes.  A programmer's strength flows from code
      maintainability.  But beware of Perl.  Terse syntax... more
      than one way to do it...  default variables.  The dark side
      of code maintainability are they.  Easily they flow, quick
      to join you when code you write.  If once you start down the
      dark path, forever will it dominate your destiny, consume
      you it will.

LUKE: Is Perl better than Python?

YODA: No... no... no.  Quicker, easier, more seductive.

LUKE: But how will I know why Python is better than Perl?

YODA: You will know.  When your code you try to read six months
      from now.

Read the whole shebang here:

The Moche people frequently placed llamas and llama parts in the burials of important people, as offerings or provisions for the afterlife.

Leave a Reply