Thanks Ching Ching. I'm OK with it, as long as it matches my description for how to determine the results of the competition.

I've just fixed the issues mentioned and also simplified the original code to improve its performance to reduce the chances of causing a time-out. Hope it's ok with you guys.

Just to clarify. Both issue 1 and issue 2 are problems related to the testing code not working properly, not merely an issue of the code being different from the description text.

For issue 2, the variable "expected_solution" is assigned the value returned by solution(returned_new_competition). So "test.assert_equals" compares the value returned by solution(returned_new_competition) with the value returned by solution(returned_new_competition), so the comparison will always return true.

To fix both issues, you may change "solution" to "score_pole_vault" in the codes where they should be changed. Use "score_pole_vault" for the coder's starting code or when the testing code references to the coder's code, and "solution" for your testing/reference code.

Hey rt-hawk, can you take a look at the issue posted above?

I'm glad you liked it so much! And thanks for creating the Python translation. I went ahead and approved it.

We had an Adidas plant in Kutztown in those days. So we were able to get their shoes at a great price, straight from the factory. The Saucony Creek runs right through the town and provided the name for the Saucony shoe brand.

Sorry, but my other katas aren't as complex as this one. So you might be disappointed. But thanks for looking at them!

Hello rt-hawk,
I'm glad you took on the challenge and completed it. As you can see, not many people have! Planning your approach before coding is definitely a good idea on this kata. The difficulty surprised even me as I was writing it. It's remarkable that pole vault officials do all of this figuring fairly quickly as they glance over the scoresheet after the competition.

Sounds like we're about the same age. I ran the 440 (yards -- it was right before they switched over to 400 meters) and graduated from high school in 1978. Coaching my pole vaulters is great fun, though I do think you have to be pretty brave to be willing to get upside down that high off the ground.

@rt-hawk :

code-wars does not allow you to delete a kata as soon as a single person (excluding author) has solved it.

The best you can do is set it to a draft by unpublishing it. Although a better solution would be resolve the issue instead. Since you are the creator of the Kata you can resolve the issue by going to the comments clicking on reply (to the issue post). There on the bottom left - just above the submit button- is the mark issue as resolved, just do that instead ?

Also kata's that were converted to drafts are not visible to anyone from the authored kata list save the author himself. So you will need to manually provide a link to it.

Read the notes in the description and the error message you are getting.

You can format your code with markdown

Is there a link you your kata draft?

Have a look at Zeroes and Ones. You already solved that. It has pretty standard random testing.

Random tests are not that hard. Generate random input, apply both user and reference solution to it, compare outputs. See the tests of most any kata you've solved - you can see them after solving.

Random tests really aren't optional in 2018.

Good job! The solution's not too long, but a nice mix of concepts within. And several possible approaches. Looking forward to part 2!