Exam PCPP-32-101 topic 1 question 21 discussion

In Python code, it is permissible to break before or after a binary operator, as long as the convention is consistent locally. For new code Knuth’s style (breaking before the operator) is suggested.

To solve this readability problem, mathematicians and their publishers follow the opposite convention. Donald Knuth explains the traditional rule in his Computers and Typesetting series: “Although formulas within a paragraph always break after binary operations and relations, displayed formulas always break before binary operations” [3]. Following the tradition from mathematics usually results in more readable code: # Correct: # easy to match operators with operands income = (gross_wages + taxable_interest + (dividends - qualified_dividends) - ira_deduction - student_loan_interest) In Python code, it is permissible to break before or after a binary operator, as long as the convention is consistent locally. For new code Knuth’s style is suggested.

PEP 8 allows line breaks either before or after binary operators, as long as the style is consistent within the project or local context. For new code, PEP 8 recommends breaking lines after binary operators to improve readability and align with mathematical notation. Example of the recommended style: result = (variable1 + variable2 - variable3)

PEP8 now (since 2016-06-08) recommends breaking before the binary operator. Even though in Python you’re allowed to break code lines before or after binary operators (providing you do so consistently and that this convention has been used in your code before), it is recommended that you follow Donald Knuth’s style suggestions and break before binary operators as this results in a more readable, eye-friendly code. https://edube.org/learn/pcpp1-python-enhancement-proposals-peps/pep-8-code-layout-1