Nice kata with very clear boundaries and just enough edge cases to keep you honest. It’s simple on the surface, but it subtly tests whether you think in terms of time units rather than raw numbers, especially around zero and formatting.

I liked how this problem encourages separating concerns: first compute the logical values (hours and minutes), then handle presentation. That distinction mirrors real-world code more than it might seem at first glance. Overall, it’s a clean, practical exercise that rewards precision and readability over clever tricks—exactly the kind of problem that builds good habits.

Haskell translation

This answer erroneously passes. It should not pass because something like Pas$w0rd// gets through, but there's no test case to catch that.

Approved

python new test framework is required. updated in this fork

.

All above issues fixed (in python)

All above issues fixed (in python)

Definitely not enough honor.

@ THByt: warning, Anter69 is talking about using the edit panel of the kata directly, but I'm not sure you have enough honor to have access to this feature. If it's not the case, you'll have to fork your translation and submit a new one.

Yes, you can:

• click on "edit kata" (top-right)
• select python (if not yet selected)
• make your changes (see more suggestions above)
• click "re-publish" (top-left)

Further suggestions for python:

• use snake_case for the function name, just make sure you keep compatibility with the older solutions, putting these lines at the top of the test block:

try:
    time_convert = timeConvert
except NameError:
    pass

• consider using random.randint for generating random integers
• also test negative numbers (e.g. randint(-100, 1000))
• consider updating the solver in the tests (see the top rated solutions)

Cheers