I've seen someone saying that Python tests are all correct, but...
I'm having trouble on a dozen tests with distinctly unexpected error logs... and it's not the case where it switches actual and expected answer!

e.g.:

2 should equal 8
Log
[937640, 767456, 981242] Start
[937640, 767456, 981242] treating
will apend 6 ** 2
[937640, 36] treating
will apend 0 ** 4
final list [0]
(my answer should be 0, but it sees as 2, and says that it should be 8,wtf?)

other cases that starts with [338340, 637600, 654608] and boil down to [338340, 0] should expected 1, right? anything powered to zero is one.

To those who got the algorithm correct but cant get around the time out, I strongly suggest reading up the 'Primality Test' article on wikipedia.
Maybe you're checking numbers you actually dont need to, and that's what's taking time.

I myself spent more time then I'd like to admit tuning the gap function while the problem resided on my custom function to find if it's prime.