exercise4/answer.py: does insert(3, 'pink') survive future edits, and is the tuple unpack intended?

[dab00gieman]

In answers/exercise4/answer.py:

colors = ["red", "green","blue"]
colors.append("vintage")
colors.insert(3, "pink")

so "pink" lands at index 3, right before "vintage" — but that position is hardcoded against the current list shape. If a future edit adds another append above this line, insert(3, ...) silently changes meaning. Would colors.insert(len(colors) - 1, "pink") express the intent ("before vintage") better, or is the fixed index the point of the exercise?

Second thing in the same file:

point = ("x=10", "y=20", "z=30")
x, y, z = point

Unpacking gives x = "x=10" (a string), not 10. The RGB example right after unpacks real integers, so was the string-tuple deliberate (just practicing unpacking), or should it have been (10, 20, 30)?

[mgkvibez]

Both flags are worth raising, and they're separable:

1. insert(3, 'pink') against a hardcoded shape — yes, fragile. The intent (from the output order) is "pink lands right before vintage." Index 3 only happens to encode that because the list is 4 long at that moment. Intent-preserving alternatives:

colors.insert(colors.index("vintage"), "pink")  # "before vintage", by name
colors.insert(-1, "pink")                         # "before the last element"

With the current sequence both are equivalent to insert(3, ...) — but they survive future appends above, which is exactly your concern. insert(-1, ...) is the smallest change; index("vintage") is the most self-documenting.

2. The tuple unpack — intended as practice, but there's a real bug in the payload. Look at the elements:

point = ("x=10", "y=20", "z=30")
x, y, z = point

Those are strings, not numbers — the quotes make x come out as the literal text "x=10", so print(x) prints x=10, not 10. The unpacking mechanics are fine (that part reads like deliberate tuple-unpacking practice, matching the navy_blue RGB example right below it), but almost certainly the intent was:

point = (10, 20, 30)
x, y, z = point

The navy_blue unpack directly below is the correct pattern — numbers in, unpacked values out — which suggests point was meant to be its twin and the quotes are a slip rather than a design choice. The grades block at the end also has a small teachable quirk: grades.sort() then print(sorted(grades)) — sorted() returns a new list, so the second print redundantly re-sorts an already-sorted list (harmless, but the two lines are teaching different things than they appear to).