not fixed.

Merged now, thanks @KayleighWasTaken for your work on this kata!

ha, yes, you were right. Rookie mistake on my part. Thanks!

Yeah I'm not wasting time debugging it for you since it's being changed anyway, but the tests are breaking due to something your code is doing.

Probably something to do with your global variables due to the implicit splat imports the runner adds everywhere.

Awesome, hoping your fork gets merged soon so I can solve. Anyways, I don't know. I started training this one today.

Well precisely none of that code is even present anymore, so yes.

I deleted the entire tests and started from scratch, only keeping the fixed cases.

How did you achieve that crash though, it didn't happen to us.

Does your fork resolve the following error in the current python tests?

Traceback (most recent call last):
  File "/workspace/default/tests.py", line 337, in <module>
    test.assert_equals(playingCards.encode(message), playingCardsControl.encode(message))
                                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/workspace/default/tests.py", line 88, in encode
    deck.append(originalDeck[cardDigit])
                ~~~~~~~~~~~~^^^^^^^^^^^
TypeError: list indices must be integers or slices, not float

Python fork with updated test framework

I refactored the tests to mirror the Scala ones I wrote at the same time, though you get nicer test grouping (Scalatest just gets in a fight with the test reporter if you try anything nested).

Great, go for it ;-)

Oh man, I just realised that you had already written here the answers to the two questions I asked you in the fork... Sorry about that, I didn't pay attention.

Thanks for doing it!

Ok. I understand your point about the printDeck function, but recreating it with the unicode characters — which looks good with some fonts ;-) — would be a pain and it's not the point of the kata.

The JS is on purpose, yes. They will display for all languages since there is no alternative block provided.

They could just have easily been any other language, I chose JS purely for the hightlighting.

I explained a bit more in the main discourse, but getting rid of those blocks is a bit complicated. The only way to really get rid of those is to add something like There is a preloaded function which will print the deck for you, see your languages solution setup/sample tests for more information, and adding the import to either the solution setup or the sample tests.

Honestly I debate the usefulness of such a function in general, in a 4 kyu the user should be expected to know how to print a collection themselves and as such I would personally remove it.

Thank you!

Nice, thank you. I notice that you have left some examples in javascript, and also all the code blocks for the printDeck functions. Is it on purpose? The description still won't be language agnostic.

Scala translation