On Wed, Mar 24, 2021 at 10:35:59PM -0000, firstname.lastname@example.org wrote:
Several attempts in this thread to write "simpler" code that does this job proved to be buggy. I feel there's some ground to say that having this in the library could prevent other less talented writers make those or even bigger mistakes.
I feel a tuple to specify multiple patterns fits nicely and it's easier to explain that an extended syntax.
I have created an issue and opened a PR with doc and tests, if this is deemed something worth to have.
Why it must be a tuple and not an iterable? Not even a list?