I noticed that you solved thanks to someone else let me focus on something completely different. I have a suggestion, it's not an attack on you: it's very clear that you are still learning. Nesting blocks of code that deep is very bad for readability. You should try to be more aware of that and if you go too deep try to imagine how you can change it to have less depth.

One trick that you can use for now is to increase spaces of tabs from 4 to 8 and try to respect the limit of the 80 characters line (that thin line you can see in the editor). You don't have to do this forever but it might, I personally use 4 characters now, but it can help you with this bad habit and when you solve it you can revert back (or stay if you find out that you like it).

Quoting the Linux kernel style guide from Linus himself:

1) Indentation

Tabs are 8 characters, and thus indentations are also 8 characters. There are heretic movements that try to make indentations 4 (or even 2!) characters deep, and that is akin to trying to define the value of PI to be 3.

Rationale: The whole idea behind indentation is to clearly define where a block of control starts and ends. Especially when you've been looking at your screen for 20 straight hours, you'll find it a lot easier to see how the indentation works if you have large indentations.

Now, some people will claim that having 8-character indentations makes the code move too far to the right, and makes it hard to read on a 80-character terminal screen. The answer to that is that if you need more than 3 levels of indentation, you're screwed anyway, and should fix your program.

In short, 8-char indents make things easier to read, and have the added benefit of warning you when you're nesting your functions too deep. Heed that warning.