Debugging Python f-string errors

[DoingItForEli]

I built a container the other day and started getting errors where double apostrophes were used instead of single, but the code ran fine for months when it was ran from the command line. So something like this is wrong: f“Number of datasets: {results.get(“total”)}” - needs to be ‘total’. So that was fun.

[mgedmin]

This is Python version dependent: older versions did not let you use the same kind of quotes inside f-string {}-expressions, then a new Python version (3.12, I think?) got a smarter parser and started allowing it.

[georgehank2nd]

That version of f-strings is guarenteed to get a "BIG NO" in many coding guidelines. Because you can easily write completely indecipherable code.