On Thu, May 28, 2020 at 11:42 AM Serhiy Storchaka <storchaka@gmail.com> wrote:
28.05.20 11:02, Ram Rachum пише:
> I recently submitted this PR
> <https://github.com/more-itertools/more-itertools/pull/430/files>, and I
> had to use assertSequenceEqual twice, just because I wanted to compare 3
> sequences to each other rather than 2.

You have wrote much more text in this message that you would save by not
typing assertSequenceEqual twice.

I see text written in emails as about x10,000 cheaper than text written in code.

> Wouldn't it be possible to make assertEqual and its entire family
> (including assertSequenceEqual and the dozen of other methods) accept an
> arbitrary number of arguments, and compare all of them to each other?
> That way I could do this:
>      self.assertSequenceEqual(sliced_tuple_0, sliced_tuple_1, sliced_range)

As Rémi said, it is breaking change.

I understand. We could slowly move towards having these keyword arguments be keyword-only arguments, with a patient deprecation cycle. This would probably be a good thing regardless. But I know that's a hard case to make here.