fïxed

expected false to be true

Is not a very useful message!

mmhm, perhaps :)

Could be another kata...?

Nice kata on dynamic programming as well except for math and combinatorics.

I also think you enjoy generating these gravestones ;)

Yeah. To confuse the devil.

disallowing recursive implementations because the function you require contains the word sort

this is easy enough to work around of course. but it's very, very user-unfriendly to enforce the restrictions this way.

there should also have been a separate test block enforcing the restrictions with normal test failures, instead of the fugly exceptions that are being raised in the course of functionality testing.

ETA: sort_array = sorted, which is a valid solution apart from the restrictions, raises the following exception:

TypeError: don't know how to disassemble builtin_function_or_method objects

that's apparently a test error, not a code error. that's just one ( but very bad ) way in which the restrictions enforcement absolutely s*cks.

unrelated, but I'll mention it here because the kata is retired anyway: there is absolutely no reason to use a fscking BubbleSort as the reference solution. you could just have used the native sort - it's not forbidden from testing!

but kata depending on forbidding native methods are almost always a bad idea anyway ( which you had been told ).

modules forbidder.

• wouldn't be enough, especially in a case like this
• the kata is already retired

• You are not peventing the use of builtin functions that way.
  Look at B4B's modules forbidder.
• You are disallowing recursive implementations because the function you require contains the word sort.

done

There are annoying deprecation messages :

assertSimilar is deprecated, use assert.deepEqual

The last two sample tests need to be changed :

n_vals = [[1, 0], [2, 3], [3, 18], [4, 60], [5, 150], [342, **420115062**], [56753, **386209565**]]

Cool one!

Another curious number :496, there are so few...