nvm, I'm pretty sure it's getting past test 8 and then I'm timing out on a different test. My problem with that is when it times out, I don't get any output besides the timeout error, so I don't know what input I'm failing on. My code doesn't have any while loops or recursion, the only thing I can think that would time it out is if a very large number is being passed in since I loop through a range to find common factors...

Other tests that time out:
if (m == []) == True:
return None

if not (m != []):
return None

if len(m) == 0:
return None

I tested that last one at returning "poop" also, and that continues to work just fine

I put: return None at the top of my function to see if the system has a problem with returning None in this case. It returned None as quickly as you would expect. I added: if m == []: return None, & it timed out again. I changed it to if m == []: return "poop" and it seems to not have a problem testing for an empty list & returning a string.
My problem only occurs when testing for an empty string and returning None when true

Whyyyyyyyyy, when I add in a test for [] or later if N == 0 the test times out after 12000ms. This is not happening on my Python shell, only on the site. Python 3.4.3 on my PC

I made this WAY harder than it needed to be. It was my first kata here & I haven't coded in python in like a year, but I think this helped me shake the rust off.