Description merge conflict. Fork the translation and manually fix the merge conflicts, then the new fork should be approvable.

Approved

Java translation submitted!

I had to fork my translation because the main description has been changed after the translation was approved. (It's not your fault, but CW's.)
I agree that the current CW platform is confusing and awkward in many ways.

Ah thanks, that was my issue. I was doing an '''import re''' for testing and left it in the solution instead of the tests part. My bad.

Ah, I just saw what you did there. I actually just amended the actual read out for that test (both the JS and Python ones) to mention what keywords are being checked for. This whole translation/fork thing is a bit confusing. Sometimes I can't even figure out which kata it is that I'm actually editing/looking at. And I don't understand how there are individual code blocks for each kata but only one generic description. Seems like that could use some improvement. Ugh, well, I have digressed...

The python version checks for re, sys, and print keywords. They are prohibited.

Updated Python translation:

• Added clarification about the 2nd anti-cheat test
• Modified the test inputs to have values up to 2 ** 31

Bubbler has already published a translation fork. Awaiting kata author to approve the fork :)

(I thought you were talking about the JS version.)

@hufftheweevil am I missing something here?

:/ I didn't know that python even had prototyping, and I'm pretty sure my solution doesn't include it.

You code contains prototype.

(I'm not sure what @hufftheweevil meant to do with that test, but it's set up like that. You'll need to ask him for clarification.)

I just finished the problem and was exited to submit, but now it fails one of the anti cheating checks and says "You're asking for trouble...". What does that actually mean, I dont think I'm doing anything illegal in my solution.