I'm not easily confused, but sometimes CompSci shit is so spread out that you have to read five different things to understand one idea. Thanks for the clarification.

Fucking thank you. That description is exactly what I wanted. I may be a beginner coder but I do understand the basics of a computer. This post was exactly what I wanted to know. If I could give you ten upgoats, I'd give you fifty. I hope my one is sufficient, and thanks for not treating me like a complete idiot.

I missed this, I replied to the person below who gave me a good answer as well.

If I could try an interpret this, Python execution ends up in bytecode and C ends up in assembly? I think I understand that all things eventually end up in assembly, but all things don't specifically go there first. Python ends up in bytecode that further migrates to assembly?

On a side note, and if you're willing to help a guy out, what's the reason for the difference? Why do I have to compile C but not have to compile Python? I guess I'm struggling with the 'why' and 'how' more than anything. From what I've heard, Python can be executed at run time. I don't exactly know what that means.

You're a goddamn saint. It worked. Thanks a million.