(Redirected from Python programming)
- And what defines a 'python activist' anyway? Blowing up Perl installations worldwide?
- Ivan Van Laningham, June 2005, on comp. lang. python
- Python is more concerned with making it easy to write good programs than difficult to write bad ones.
- Steve Holden, June 2005, on comp.lang.python
- Everyone has an individual background. Someone may come from Python, someone else may come from Perl, and they may be surprised by different aspects of the language. Then they come up to me and say, 'I was surprised by this feature of the language, so Ruby violates the principle of least surprise.' Wait. Wait. The principle of least surprise is not for you only. The principle of least surprise means principle of least my surprise. And it means the principle of least surprise after you learn Ruby very well. For example, I was a C++ programmer before I started designing Ruby. I programmed in C++ exclusively for two or three years. And after two years of C++ programming, it still surprises me.
- Yukihiro Matsumoto "The Philosophy of Ruby, A Conversation with Yukihiro Matsumoto, Part I" by Bill Venners on 2003-09-29 (Artima Developer
- Excellent plan! Devious minds are attracted to Python, like mimes to unappreciative crowds.
- Tim Peters, 13 Nov 1998
- Python's syntax succeeds in combining the mistakes of Lisp and Fortran. I do not construe that as progress.
- Python is an experiment in how much freedom programmers need. Too much freedom and nobody can read another's code; too little and expressiveness is endangered.
- Guido van Rossum, 13 Aug 1996
The Zen of Python (from the output of "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.
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