4.2 Structure of a Python Program

Program Layout

What Is It?

The conventional top-to-bottom ordering of sections in a Python file.

Why Is It Used?

A predictable layout means any Python developer can open an unfamiliar file and immediately know where to look for imports, config, and logic.

How Is It Used?

Imports first, then module-level constants, then function/class definitions, then the entry-point guard at the very bottom.

Execution Flow

How Does It Work?

• Python executes a script’s top-level statements in order, one at a time.
• def and class statements don’t run their bodies immediately — they just define the function/class for later use.
• This is why the entry-point guard at the bottom is what actually kicks off the program’s real work.

Entry Point

What Is It?

The if __name__ == "__main__": block is Python’s convention for “only run this if the file was executed directly, not imported.”

Why Is It Used?

It lets a file be both a runnable script AND a safely importable module — without it, importing the file elsewhere would immediately re-run all its top-level logic.

def main():
    print("Running as a script")

if __name__ == "__main__":
    main()

# If this file is run directly:   $ python3 script.py  -> prints the message
# If this file is imported instead: import script       -> main() does NOT run

Writing Readable Code

What Is It?

Structuring code so its purpose is clear without needing extensive comments — meaningful names, small functions, consistent formatting.

Why Is It Used?

Code is read far more often than it’s written; investing in readability up front pays off every time someone (including future you) revisits it.

Quick Interview Answer

“A Python file conventionally follows imports, then constants, then function/class definitions, then an if __name__ == '__main__': guard at the bottom. That guard is what lets the same file work both as a standalone script and as a safely importable module, since def/class only define things — they don’t execute their bodies until called.”

Common Mistakes

• Putting real logic at module level, outside any function or the __main__ guard — it then re-runs every time the module is imported elsewhere.
• Forgetting that a def block doesn’t execute anything by itself; it only defines a function to be called later.