Commit 92815cc
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -584,9 +584,9 @@ exhaustive test suites that exercise every line of code in a module. | |||
| 584 | 584 | An appropriate testing discipline can help build large complex applications in | |
| 585 | 585 | Python as well as having interface specifications would. In fact, it can be | |
| 586 | 586 | better because an interface specification cannot test certain properties of a | |
| 587 | - program. For example, the :meth:`list.append` method is expected to add new elements | ||
| 587 | + program. For example, the :meth:`!list.append` method is expected to add new elements | ||
| 588 | 588 | to the end of some internal list; an interface specification cannot test that | |
| 589 | - your :meth:`list.append` implementation will actually do this correctly, but it's | ||
| 589 | + your :meth:`!list.append` implementation will actually do this correctly, but it's | ||
| 590 | 590 | trivial to check this property in a test suite. | |
| 591 | 591 | ||
| 592 | 592 | Writing test suites is very helpful, and you might want to design your code to | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -24,7 +24,6 @@ Doc/c-api/typeobj.rst | |||
| 24 | 24 | Doc/c-api/unicode.rst | |
| 25 | 25 | Doc/extending/extending.rst | |
| 26 | 26 | Doc/extending/newtypes.rst | |
| 27 | - Doc/faq/design.rst | ||
| 28 | 27 | Doc/faq/gui.rst | |
| 29 | 28 | Doc/faq/library.rst | |
| 30 | 29 | Doc/glossary.rst | |
0 commit comments