Change handling of iterable objects for on field in joins

The on field complained when I passed it a Tuple. That's because it saw that it checked for list exactly, and so wrapped it into a list like [on], leading to immediate failure. This was surprising – typically, tuple and list should be interchangeable, and typically tuple is the more readily accepted type. I have proposed a change that moves towards the principle of least surprise for this situation.