Bro, thank You so much! The description is awful AF. Without You I would skip this kata...

i did the same mistake :) mixing between diameter and radius , One should always focus while reading !

Thank you for this explanation. I am realive new to javascript and I was confusused.

64 minutes here. A bit long, I'd say.

Blocked access into midpoint rounding was like a kick between legs.

Ahh! What a silly mistake, thank you :)

Thanks!

Slightly modified the description. Thanks for your posts.

Rotate four times is only for the given example. Please can you say what I should add.

It sort of looks like you mashed your hands on the keypad, got lucky, then passed the kata.

What?! I thought that's what everybody did?

Why doesn't my line 'name is None' handle this issue then?

Because that's not the way to address it. hello(None) and hello() are not the same. I would say google the error message but the results that search gives is not that helpful either. Try looking for optional arguments in Python (that's what the kata difficulty is about).
Use question label next time if you don't know how to do things, issue is for problems with the kata (and always look at the amount of completions in the language you're trying first, if some people solved it, most probably it's a problem with your code, not the kata itself).

1. When you attempt there are more fixed tests than when you run.
2. You write too much to the console so you overflow the buffer. You could simply print to the console the input and verify by hand.
3. You don't need BigDecimal.
4. There could be an error in your code: the expected answer is 2 for the given test. See the top of the page: 368 guys passed the Java kata if there were errors in the tests somebody would have seen them. Morevoer when you attempt, the fixed tests are the same in all languages and more than 2000 guys passed the kata for all languages.
   Hope that help. Cheers.

Try this ;-)

https://docs.python.org/3/tutorial/floatingpoint.html#tut-fp-issues

Also it should be 5 is not divisible by 2, corrected.

It's a natural phenomenom of floating point numbers because you cannot represent values with 2 decimal places exactly in floats (as 5 is not divisible by 2).

The test for 2.675 should've never been in there in the first place. I've removed it from the sample tests. The actual tests never have it anyway so you can just submit as normal ;-)