This past week saw the release of Python 3.0 (final). While code you maintain will probably be compliant with one of the 2.x releases, newer code and new projects will increasingly be written in the new 3.0 syntax. If you are wondering: "What 3.0 syntax?" You are in for a surprise. The full list of changes are too many to number here, but they include such prominent aspects as Python's print facility and many of the Python modules.
To give some idea of how wide-sweeping the changes are, consider the print change alone. The old style was
As mentioned previously, all Python code will not (and certainly need not) change to 3.0-style syntax overnight. But you can expect the new syntax to appear in projects with increasing frequency in the future.
To give some idea of how wide-sweeping the changes are, consider the print change alone. The old style was
print "Hello, world!"
But with 3.0's new syntax, print is now a function, as in C. For the same effect above, you will now need to type
print("Hello, world!")
To get up-to-speed on the changes, you will do well to read Guido van Rossum's digest "What’s New In Python 3.0".
As mentioned previously, all Python code will not (and certainly need not) change to 3.0-style syntax overnight. But you can expect the new syntax to appear in projects with increasing frequency in the future.

Hehe, let’s put a ‘;’ at end of new print syntax, so then we can go back to the old C times
Just kidding, python is my favorite language, and it is because of productivity and easy/clean code reading.
It is almost like that, isn’t it? Nonetheless, I’ll take Python’s native support for associative arrays (i.e., dictionaries) over C’s DIY approach anyday.