CodecInfo objects *are* tuples for backwards compatibility reasons. Also it's still possible that codecs.lookup() returns a real tuple (however all standard encoding go through encodings.search_function() so if codec.getregentry() returns a real tuple this gets upgraded to a CodecInfo object.)

I've changed the docstring in r56456, so that it mentions both tuples and CodecInfo objects.