Top one is actually quite good. If it were for real, I would write it as a proper named function. That way is real nice for avoiding duplication, and something I didn't think of.

def is_palindrome(s: str):
    processed_text = ''.join(c for c in s.upper() is c.isalpha())
    return (lambda x: x == x[::-1])(processed_text)

100% cursed. Love it.

24 characters shorter, and I respected proper formatting rules (still a joke solution though).

nice!

Gross, good luck with maintainability or comprehension. This isn't code golf.

Better than my own, very good

It's also a game/challenge, and these are all good opportunities to learn different methods to do things. And in a production environment might not have the option to change language but can still make the code run faster where and how we can.

Ok, but this kumite uses python in tests and I'm too lazy to write a translation to C.

If I was worrying about the cost of operations like division, I wouldn't be using Python.

If you know what format the temperature is coming in already, you can just check it against the type to convert to. There is no such thing as "both". It is one or the other. Whenever you use both, the calculation for the same type of temperature will always be wrong (input fahrenheit, convert with "both", output fahrenheit will be different because it was treated as celcius).

EDIT: Ok, I see - it is tested upon and expected to work that way. Still a dumb idea. One will always be wrong, why bother.

I'm with you, this wasn't useful.

This works. Better to save the computation to a variable so you don't have to perform it twice. You can do this without regular expressions as well, which (in this simple case) is probably better.

mid

tbh it looks mid

Division is a slow operation, it's a way to reduce its usage.