Linked by Thom Holwerda on Thu 9th Oct 2008 21:04 UTC, submitted by ganges master
General Development Python 2.6 has been released on October 1st. The major theme of this release is preparing the migration path to Python 3.0, a major redesign of the language. Whenever possible, Python 2.6 incorporates new features and syntax from 3.0 while remaining compatible with existing code by not removing older features or syntax. See the what's new docs for more details.
Thread beginning with comment 333131
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Though a code that lacks a semicolon somewhere probably won't compile, (so debugging might be the wrong word) the compiler can sometimes give very long, and very unhelpful error messages when forgetting a semicolon. This is worse in C++.

Reply Parent Score: 2

evangs Member since:

When I was an undergraduate one of the modules I did required me to write a Java compiler. To make things "easier", I logged the error messages as numeric codes. While it appeared to be a good idea at the time, it soon became obvious why this approach sucked.

If you had used my compiler to compile your Java code and received an incomprehensible error message, is it Java's fault or is it my compiler's fault?

Reply Parent Score: 3

righard Member since:

I like the C and C++ syntax allot, I did not mean do blame the fault on them. But because both languages have a rather liberal syntax, it can sometimes be impossible for a compiler to guess what the user meant to do. That is just an inevitable side effect of a liberal syntax, Pyhtons syntax prevents this side effect, with the down side that I ca'n't, in my opinion intend code properly.

Reply Parent Score: 1