because despite having its dangers, the solution is beautiful to see, in the context of codewars, this type of solution comes out ahead... multiple 'ifs' are sometimes not very elegant..

I just read some comments below that clearly state you shouldn't use eval() for these kinds of purposes because eval() will
run absolutely anything, therefore it's potentially extremely hazardous to use it. So, explain to me: why the 724 Best Practices?

Nice!

convert value1 and value 2 to strings first. Your code doesn't evaluate the values of value1 and value2. Say value1 = 1 and value2 = 3, your code is trying to evaluate value1 + value2 whereas it should be evaluating 1 + 3.

clever, I'm borrowing this!

liveing on the edge

thanks for saving my data dude!

yeah easy but unsafe

Yeah, I never knew about this function. I'm going to have to read up on it. I used a bunch of match: case: statements.

It's simply easier on the brain to read code top-down. 121 char length > PEP8 limit.

• What criteria you use to determine when flexing is great?
• What makes this code not meet those criteria?
• What alternative do you suggest?

People love to flex with one-liners, and sometimes they are great... but other times like this one, bad practice.

I see, thanks alot