Suggestion: Increase flexibility for Python string formatting in curriculum tests

Contributors
1

Hi everyone,

I’ve noticed across several Python projects (such as the Movie Ticket Booking Calculator) that the automated tests are often quite strict about how strings are formatted in print() statements.

Currently, many steps require the use of commas for multiple arguments, e.g., print('Price:', price). However, using modern f-strings like print(f'Price: {price}') often causes the tests to fail, even when the final output is correct.

Since f-strings are considered a “best practice” in modern Python (PEP 498) for readability and performance, I suggest updating the underlying test regex to allow for multiple valid formatting methods (f-strings, .format(), and commas). This would make the curriculum more flexible and better aligned with how developers write Python today.

Has there been a specific reason for keeping these tests so strict, or is this something the contributor community could help update?

2

I think you should check the fCC github to see if issue have been opened for these scenarios (usually they are opened per specific test when someone reports a problem).
(it sounds like it may be an oversight but without checking on github, that’s just a guess)