For Python, the example code in the Instructions tab is not properly indented, and results in IndentationError being thrown if executed as-is.

(1) You have a method called "coords" which returns x & y coordinates. Internally, however, init() uses the terminology "cords". These should match in naming convention...so either change the method name to "cords" or change the internal variables to "coords".
(2) Capitalization: the test case instantiates as Walker() but the starter code uses class name "walker()". The starter code needs to match the test cases.

Other than that, fun kata...

Why does Voile keep repeating "not an issue" for these suggestions? It IS an issue. A kata's description should be as clear as possible and describe exactly what the return type should be (see the problems at HackerRnk for a good example of this). Having to figure out the expected return type from the single test case is not really 7th dan material.

I'm having trouble passing the basic tests. I have defined the Shape class and all the other subclasses. However, when I run the tests I get the following. I dont know from the test code what is being compared with what (at least I think something is being compared, since the error complains about '<').

Test Results:
Base class checks
Test Passed
Shapes are sortable on area
Base class check
Test Passed
STDERR
Traceback (most recent call last):
File "main.py", line 44, in
actual.sort()
TypeError: '<' not supported between instances of 'Square' and 'Circle'

Wondering how exactly this is Object Oriented?

It's still broken.

Yep, I see the same thing. Please fix.

Particularly true for Python, where None is a keyword

Seems like this is 8 kyu, not 7

way too easy to be 7th kyu. Should be 8th kyu.

Technically, the description should say:
calculate how many times the words "Sand", "Water", "Fish", OR "Sun" appear

instead of:
calculate how many times the words "Sand", "Water", "Fish", AND "Sun" appear

No, it's not just you who does very little math in daily life. I have an MSEE and there was a lot of math during those studies, but as a software tester and I use math almost never. This problem seems like it belongs on Project Euler.

Agreed. The answers array has one not-answered element (worth 0) and 3 incorrectly-answered elements (each worth -1). I don't know why the test expects 0.