While we're fixing things: "the LCD's on the market can't match its picture."

Don't forget MySQL's translation of NULLs in NOT NULL constrained fields to 0 or empty strings instead of rejecting the update as a proper RDBMS should. Somebody needs to explain to them that missing data is missing, not 0. I can't tell you how many problems I've seen this cause (ofc, whether and how NULLs should be used is another discussion entirely...).

Let's not forget how it "enforces" constraints. For example, consider:

CREATE TABLE emps (id INT(10) AUTO_INCREMENT,
fname VARCHAR(50) NOT NULL,
sname VARCHAR(50) NOT NULL);
INSERT INTO emps (fname) VALUES ('John');

In a proper RDBMS, that would fail for violating a constraint. MySQL/MariaDB just massage the missing sname into an empty string, which is about as valid as just sticking 'sldfjpsdj;ksdj;fsdljkfsd.'

Just to be a pedant, nobody owns RIM shares anymore. They might, however, own BBRY shares.

That would be a backdoor in the compiler, not in Python (or CPython more properly, since Python proper is a spec, not an implementation, which is why the question is really, really meaningless).

That's one of Guido's concerns in the blog post I linked.

What does that even mean? It's a programming language, not an application or operating system. Do you mean crippling certain functions in the standard library? It's all open source.

FWIW, IronPython and Jython are GIL-free, but IronP is no longer maintained.

Exactly. It's terribly unpythonic. Sadly though, I don't have a better way to do multi-line lambdas.

You've stated (http://neopythonic.blogspot.com/2009/04/tail-recursion-elimination.html) that you consider tail recursion to be "unpythonic." Could you elaborate on that a little more. What about algorithms that are by their very nature recusive? I've found that a combination of memoization and tail recursion can, under the right circumstance, provide wonderfully clear code without taking too much of a performance hit, and Python's decorator facility always seemed more or less ideal to me for that sort of application.

If you could go back to the very start and change one thing about Python, what would it be and why?

IronPython and Jython have no GIL. Unfortunately, IronPython is no longer being maintained and the last release was over a year ago.

One of the most common complaints about Python is the limitations of its lambdas, namely being one line only without the ability to do assignments. Obviously, Python's whitespace treatment is a major part of that (and, IIRC, I've read comments from you to that effect). I've spent quite a bit of time thinking about possible syntax for a multi-line lambda, and the best I've come up with is trying to shoehorn some unused (or little used) symbol into a C-style curly brace, but that's messy at best. Is there a better way, and do you see this functionality ever being added?

Python does support threading. The issue is that CPython implementation has the GIL to contend with. IronPython did away with the GIL, but it's no longer being maintained. Also, http://interviews.slashdot.org/comments.pl?sid=4105821&cid=44608065 beat you too it.

As somebody else has pointed out, it's a <tt> tag. That tt stands for "teletype." That your system (and mine) happen to represent that with courier doesn't change the fact that it's a typewriter font. Monospace is great for code, but pretty lousy for actually reading.