Which of these are synonyms for Python's comment symbol #?

Select every option that applies, then check.

• Octothorpe
  Correct. The reading calls # "the Octothorpe" — one of its traditional names.
• Exclamation
  Not quite. The exclamation mark is !, used for negation in some languages and shebang lines, not as a name for Python's comment symbol.
• Sigil
  Not quite. A "sigil" is a general term for a symbolic prefix character (like $ in some languages) — it isn't one of the names the reading uses for # specifically.
• Hash
  Correct. The reading names # "the Hash symbol".
• Decorator
  Not quite. A decorator is a Python feature written with @, unrelated to comments.
• Variable
  Not quite. A variable is a name that stores a value — it has nothing to do with the comment symbol.
• Print
  Not quite. print is a function that displays output; it isn't a name for #.
• Pound Sign
  Correct. The reading also calls # "the pound sign".

According to the reading's advice, which of these scenarios justifies leaving a comment in your program?

Select every option that applies, then check.

• A syntax error is breaking your program, so you comment that code out
  Not quite. This describes commenting out code without explaining why. The reading calls commenting-out code "generally bad practice" unless you also leave a comment explaining what the old code was for — silently commenting out broken code doesn't meet that bar.
• One line of code works, but it is somewhat confusing despite all your attempts to make it more clear; you want to explain how it works.
  Correct. This is exactly the reading's "reasonable middle ground": write comments for code that is unexpected or surprising, even after you've tried to make it clearer.
• Every line of code should be commented, so that anyone can read the code.
  Not quite. The reading explicitly rejects this "extreme opinion" of commenting every single line.
• Never leave a comment, it's a useless feature
  Not quite. The reading also rejects this opposite extreme — comments are useful for explaining confusing code.
• You have some old code that you no longer need, and want to remove it from your program with a comment.
  Not quite. The reading says "removing code using comments is generally bad practice," and its advice is to "remove any comments that don't help explain the existing code." Old code you no longer need is exactly that kind of comment, so the reading's advice is to remove it, not to leave it there.