I like your solution it takes really small amount of time in comparison with string format operation. My solution takes 3-4 times more than yours 🙂 but current one with string format takes 2-3 times more than mine 🙂. String formatting really heavy operation even in this case when we have to format 10 numbers only

Thank you for this feedback, I've been wondering where the sweet spot of documentation is. I've had the idea of explain like no one has any idea what anything does. But it does seem to annoy seasoned developers. I've been playing with the idea of writing comments on blocks of code instead. My level of discernment is not high enough to figure out what doesn't need be said, yet.

Looking at your solution it looks like you just like to add documentation for the sake of documentation, even when it results in illegible code and a ton of duplication/stating what is obvious even to novices. I won't claim the top solution to be best practices, but less is more in this case when the solution can be whittled down to a single standard lib function call.

Super clever absolutly, Best Practices not even close. Where is your documentation.

Get a bigger python.

no 'trick'

I'd be very surprised if Python was the only tool to have a frame inspector in its librairies.
You're welcome to write the translations :)

"Don't even try"

Distance is euclidean distance. What kind of distance were you thinking of?

I am sorry to bring this up again; but it still isn't clear from the description what distance means in the context of the kata.

This needs a graph or a formula, or something.

I'm sorry if I come accross as a little rude, I appreciate the work of anyone that takes the time to create katas, but I've just spent way too long drawing a circle just because I didn't know how the hell I was expected to count.

Oh no, 'tis me that is the fairest of them all !

I just love to print,
and then print some more.