Babo's right--remember that Python is "batteries included," which means all the standard libraries (which cover a huge range of uses) are already 3.0-ized.
Good point. But http://www.python.org/download/ says in its discussion of 2.6/3.0: "if you don't know which version to use, start with Python 2.6." To me, this advice is inconsistent with the layout on the front page, since most people who don't know what to use will click on the 3.0 link.
They could be going for two different types of user:
A) Brand-new programmer or language nomad who wants to dive right into Python. It's for personal enrichment, so they might as well learn the latest dialect and not pick up archaic habits.
B) Wary/professional programmer, or someone who wants to get something else done and thought Python might do the trick. This is the user who will actually bother to stop and read the instructions on the download page, probably because something else they want to use says it requires Python. (Perhaps a library with skimpy documentation.) If it works right away, they'll keep using Python; if not, they'll probably blame Python as a whole instead of the particular version they downloaded and use some other language to solve their problem.
Anyone in charge of a real production system is presumably beyond the "I guess I'll try Python" stage and is able to find out exactly which version they need.
