Pretty much yes. dicts are something completely separate from list-like types. Those should not be mixed.
lists and tuples depend on your preference really, but I appreciate them being available. There are many places where you want to pass an immutable sequence of objects and the list is just not right... Sure we could get rid of them, but what would be the gain there?
I don't need more and I don't need less: the two seem well-balanced for me.
As someone who abhorred Perl, Ruby looks a little frightening. Python looks and feels clean, especially for blocks of data.
In OO though, self.whatever appears more frequently than I'd like.
While I agree that tuples and lists could be merged, I don't think that dicts should be merges with them, too.
When I first looked at PHP I found the concept of having a unified "array" type (for arrays and hash tables) very clever. However, I quickly changed my mind.
Now I think that the array/hash unification is one of the biggest design mistakes in PHP as it provides no benefit (both have completely different use cases), but causes a lot of trouble.
A similar argument goes for ECMA Script (aka JavaScript).
Granted, a lot of languages like Ruby, Lua, ML and even CoffeeScript have arguably even cleaner syntax then Python, but none has as vast a community and quality libraries that mirror Python. In choosing a language, the language itself matters, but the ecosystem equally matters IMHO.
But Python has still the cleanest standard API. At least for me, that's what made me switch from Ruby to Python in the past.
Python seemed really refreshingly clean compared to Perl and C++, the languages I'd been using previously. I still think it's a decent language, but Python is to Perl and Lua is to Python along those lines. I've moved on.
I'm probably still just annoyed about Guido's position on tail-call optimization, though.