нет необходимости переписывать функцию, взгляните на литкод. оператор % тоже устарел, однако его продолжают использовать)

there is no reason for the "special rule" to be buried at the bottom of the description, after the I/O and examples. it makes it harder to see all rules at a glance; it forces one to have to scroll back to the beginning of the description

since Python 3.9, type hints such as List, Tuple or Set are deprecated in favor of using types directly, e.g. list[str] or tuple[int, int]. the initial code should be rewritten in consequence

Preloaded func signature looks like leetcode

Under the section "Determining the winner" I mentioned that low aces are valid, implying the allowance of low ace straights.
I can textify the image if its a problem.

I accidently created a solution that does not always pass the random tests.
https://www.codewars.com/kata/reviews/6255e73cea4e7f004a79ed68/groups/66b37a14f8be82e8ded15341

I think my kata explains the problem a little better and more clearly

I don't see how your kata's explaining the task better or more clearly when you only dump a image. If the image dies, nobody can read the rules anymore.

Also, both katas fail to mention clearly whether a wheel (low ace straight) is considered a straight. It's complicated; it's generally allowed in standard poker variants (including Texas Hold'em) but not explicitly stated, while some lowball variants disallows it.

I am programming a complete poker game.
The kata you mentioned does lack some useability since it does not cover the whole picture.
I think comparing multiple players was fun and its necessary in an actual program.
Altough subjective, I think my kata explains the problem a little better and more clearly.
Thank you for looking into this.

How do I add random tests? Because I already have a random generator locally.

There are no random tests.

There's already a kata that does 95% of the job (evaluating the highest possible hand for a player).

The remaining is just computing a total order and comparing this score, which is a trivial addition compared to the task. So I'm tempted to call this a duplicate.

You are missing something, the kata is ok.

You should raise it as issue.

(i cry everytime)

n = 1: expected 7 to equal false
n = 1: expected false to equal 7

It expects 2 different outcomes for the same input?
Please fix because this is currently an unsolvable kata