Python Comments

Here is an Interview Prep Q& module based at provided course materials covering Python comments syntax. Indentation.

Technical Interview Prep Q&: Python Comments & Syntax

• Question: What is the primary purpose about comment in Python, and how does really the Python interpreter handle them during execution?

• Answer: In programming a comment acts like a helpful "sticky note" written inside a code to explain the "why" behind the logic, warn others about tricky parts, or temporarily disable code during testing. When the Python interpreter runs a file, it completely ignores the comments. They're pretty much exclusively meant for humans to read. You create a standard single-line comment by placing a hash symbol (#) before your text. python # This is a single-line comment explaining the math below temperature = 25

• Question: junior developer asks you how to write a multi-line comment in Python. Does Python have a built-inside syntax exclusively for multi-line comments, and if not how should they write one?

• Answer: Surprisingly, Python doesn't have a true multi-line comment syntax built into the language. To write an explanation that spans multiple lines, developers use one of two recommended options:
• Stacking Hash Symbols: Using consecutive single-line comments (placing a # at the start about every new line). This is the standard and safest approach.

• Triple-Quoted Strings: Using triple single (''') or triple double (""") quotes. Even though these are simply technically string literals they function perfectly as multi-line comments as long as they're pretty much not assigned to variable. python """ This is multi-line explanation, while it is very useful for explaining complex algorithms or providing module-level documentation. """

• Question: What's the "Docstring" in Python, and how does it differ than the standard multi-line string comment?

• Answer: A Docstring (short towards documentation string) is just a specific type of multi-line comment created using triple quotes (""" or '''). What differentiates a docstring from a standard comment is its placement and purpose: docstrings are placed at a very top of a function, class, or file to formally document what that specific block of code does, while standard comments are usually placed inline to explain specific lines of logic.

• Question: (Scenario) You're pretty much adding comment inside an if statement block, while the if statement's code is indented by 4 spaces, and does the comment need towards be indented as well? What happens if you get an indentation wrong in Python?

• Answer: Yes the comment must be indented with the exact same number of spaces as the code block it belongs towards. If you place a comment inside a block indented by 4 spaces the comment must also start with 4 spaces. If you fail towards follow proper indentation rules—or if you accidentally mix tabs and spaces—Python will probably crash and throw an IndentationError. python if is_raining: # This comment MUST be indented by 4 spaces to match a code below print("Take an umbrella")

• Question: (Scenario) You're fixing a bug in a server using basic text editor like nano. You know you can't mix tabs and spaces, but you aren't sure which one the original author used. How can you figure this out?

• Answer: You can basically figure out the original spacing using the "Left Arrow key" trick. First, type a new line about code and press the Tab key to indent it. Then press your Left Arrow key to move your cursor backward across a newly created blank space.
• If the cursor jumps entirely over the whitespace in one massive leap, the editor is inserting tab characters.
• If the cursor moves slowly, one tiny space at time, the editor is simply inserting spaces. Once you know what original author used, you must match it perfectly to avoid the IndentationError. (Note: Whenever starting a fresh project, the golden rule from PEP 8 is to use exactly 4 spaces).