8000 gh-96265: Fix some formatting in faq/design.rst by slateny · Pull Request #96924 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

gh-96265: Fix some formatting in faq/design.rst #96924

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Oct 7, 2022
Merged

gh-96265: Fix some formatting in faq/design.rst #96924

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
c085851
Fix some formatting in faq/design.rst
slateny Sep 19, 2022
c300f88
Use links instead of literal
slateny Sep 19, 2022
a96893a
Add back quotes
slateny Sep 19, 2022
a7542ba
Add more proper refs
slateny Sep 21, 2022
2d68707
Add formatting for walrus operator
slateny Sep 21, 2022
399564c
Use list.append instead of append, if-else -> if/else
slateny Sep 22, 2022
e110dd1
Wrap long line
slateny Sep 22, 2022
ce33989
Remove literal from big-O
slateny Sep 23, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Use list.append instead of append, if-else -> if/else
  • Loading branch information
@slateny
slateny committed Sep 22, 2022
commit 399564cd153d582f4f184a067839e4506e09ff15
6 changes: 3 additions & 3 deletions Doc/faq/design.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -584,9 +584,9 @@ exhaustive test suites that exercise every line of code in a module.
An appropriate testing discipline can help build large complex applications in
Python as well as having interface specifications would. In fact, it can be
better because an interface specification cannot test certain properties of a
program. For example, the :meth:`append` method is expected to add new elements
program. For example, the :meth:`list.append` method is expected to add new elements
to the end of some internal list; an interface specification cannot test that
your :meth:`append` implementation will actually do this correctly, but it's
your :meth:`list.append` implementation will actually do this correctly, but it's
trivial to check this property in a test suite.

Writing test suites is very helpful, and you might want to design your code to
Expand All @@ -603,7 +603,7 @@ In the 1970s people realized that unrestricted goto could lead
to messy "spaghetti" code that was hard to understand and revise.
In a high-level language, it is also unneeded as long as there
are ways to branch (in Python, with :keyword:`if` statements and :keyword:`or`,
:keyword:`and`, and :keyword:`if-else <if>` expressions) and loop (with :keyword:`while`
:keyword:`and`, and :keyword:`if`/:keyword:`else` expressions) and loop (with :keyword:`while`
and :keyword:`for` statements, possibly containing :keyword:`continue` and :keyword:`break`).

One can also use exceptions to provide a "structured goto"
Expand Down
0