Hi, Paul — that's very kind of you, thanks! I got into a rhythm with these things a couple of weeks ago, and just had at them like a lunatic. Just as cosmic inflation forever forbids us from ever keeping up with the universe's expansion, I'll never overtake your mad code challange accomplishments, but I'll keep at 'em. Congrats on your sparkly new job, and I hope you're having other-worldly amounts of fun there!

Hey Alan it's Paul! I see you're completing a great deal of code challenges on here! Just wanted to say congrats, respect and I'd better watch out, you're going to overtake me any day here!

There is a big difference between frustration because something is difficult and irritation because something is asinine. The former is par for the course with programming, the latter is bound to happen sometimes, but better avoided when possible.

Sorry about that, I meant having extra edge cases on purpose, such as 1 digit numbers not being a palindrome, makes the kata less enjoyable while not really adding anything. There are kata which focus on input validation, which is fine, but to have extra input validation steps that don't need to be there when this is not the focus of the kata takes away from the experience. It's not a huge deal, but reading through the other comments it looks like I'm not alone in feeling this way. I appreciate the time people volunteer to make kata, hope the feedback is helpful and again sorry for the vagueness!

The tests aim to check the validity and completeness of a solution. They don't aim not to irritate you.

Uh, would you mind elaborating?

Suggest not having awkwardly forced edge cases. They should arise naturally from the problem, otherwise they are just irritating.

"A well posed problem..."

versus (see discourse immediately below) "The desciption is extremely vague..."

LOL. It is hard to please everybody. I'm glad you liked it :-)

Awesome kata, thanks! A well posed problem with lots of interesting design decisions to consider. Looking forward to improving my rather ugly solution to an elegant problem!

Hi I am getting the test crash error:
Test Crashed
Caught unexpected signal: SIGFPE (8). Erroneous arithmetic operation.

Can someone help me with this? I have tested for the corner cases such as 0 division cases. What could be my problem?

You can increase the recursion limit (in your solution) by importing sys
and using sys.setrecursionlimit()
Probably not recommended, but it sure feels good thwarting Guido Van Rossum's will. Sorry Guido.
The problem with learning recursion is that the examples that are easy(ish) to understand,
are usually terrible examples of how to actually use it.

Looking forward to doing this one! I have a history of mathematics book that goes into great detail about Egyptian fractions in the second chapter. It's been a while since I looked at that book, but I remember it being fascinating!