The latter ones because you can start to get them to deploy/work on websites. Being able to write websites is a generally useful skill nowadays (even if you don't go into programming.. all my family need/want websites, for example).
I teach an after school IT club and a project to maintain/develop a site on the school intranet has consistently been the favourite :) Because it's something functional and visible!
(and also a good opportunity to teach about security issues what with the trial-by-fire environment a school brings :D)
EDIT: the other good thing about web-dev is that it needs a few different skills - design, back-end coding, infrastructure/sysops and databases which a) gives them a taster of all the career opportunities and b) lets different people "shine" in different areas, and contribute their strongest skill to the final project.
The sad state of client-side programming is that you need to learn a lot about the messy world of HTML, CSS and JavaScript. Come to think of it, CoffeeScript might be a good language to start with today?
In my experience PHP or Ruby is generally a better/easier web programming experience (I tried Python but it never really clicked with the kids).
Python is a good general purpose language though.
But as I said earlier in the thread. We shouldn't teach them programming, or specific languages. We should teach them general problem solving.
I've taught my daughter a little bit of programming when she was younger -- I tried her with Visual Basic and we built a app that did some computation -- and she really enjoyed it. It gave her an appreciation for what I do.
So I really think that programming is generally an enjoyable experience. That's not to say we aren't exceptional, but there are exceptional people in all sorts of pursuits.
Except BASIC. Anything but BASIC.
If I had to pick a language to teach 9-10 year olds, I'd probably go with Python. Of the 'real languages' (by which I mean languages substantially used in industry/academia for real applications), I think python has the least overhead to get your head around before you can write functioning code.