If nothing else, a good way to prototype it and see if folks like it. I agree that there may be little reason to make this part of the builtin tuple.

 

not in my opinion -- Python is not a statically typed language, I will be really sad if the future of Python development was motivated by ease of static typing.

Now that I think about, namedtupled are not typing friendly either -- part of their point is that you can use one everywhere a tuple is expected. As soon as you type something as expecting a particular namedtuple, you've just broken that.

As for the memory growth -- would it need to be a new type? yes, namedtuples are types, but could we have a "tuple_with_attribute_names" that wasn't a distinct type, but rather, dynamically accessed its fields? I suppose that would be a lot heavier weight than a tuple, so maybe the same issue.

-CHB