Skip to content

Commit bf1dcf5

Browse files
committed
run fix_dunder.py, update images
1 parent 1771760 commit bf1dcf5

File tree

5 files changed

+3
-2
lines changed

5 files changed

+3
-2
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,3 @@
1+
*.bkp
12
.DS_Store
23
public/

content/_index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,4 +10,4 @@ including:
1010
- [**Extra content**](/extra/): new or updated sections that did not fit in the Second Edition.
1111
- [**Python lingo**](/lingo/): technical terms and slang used by Pythonistas.
1212

13-
![Cover of Fluent Python](/images/fluentpython2e-cover.png "Cover of Fluent Python Second Edition, illustrated with a desert lizard (Pedioplanis namaquensis).")
13+
![Cover of Fluent Python](/images/fluentpython2e-cover-drop-shadow.png "Cover of Fluent Python Second Edition, illustrated with a desert lizard (Pedioplanis namaquensis).")

content/extra/classic-coroutines/index.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -576,7 +576,7 @@ caller:: PEP 380 uses the term "caller" to refer to the client code that calls t
576576

577577
[TIP]
578578
====
579-
PEP 380 often uses the word "iterator" to refer to the subgenerator. That's confusing because the delegating generator is also an iterator. So I prefer to use the term subgenerator, in line with the title of the PEP—“Syntax for Delegating to a Subgenerator.” However, the subgenerator can be a simple iterator implementing only `__next__`, and `yield from` can handle that too, although it was created to support generators implementing `__next__`, `send`, `close`, and `throw`.
579+
PEP 380 often uses the word "iterator" to refer to the subgenerator. That's confusing because the delegating generator is also an iterator. So I prefer to use the term subgenerator, in line with the title of the PEP—“Syntax for Delegating to a Subgenerator.” However, the subgenerator can be a simple iterator implementing only `+__next__+`, and `yield from` can handle that too, although it was created to support generators implementing `+__next__+`, `send`, `close`, and `throw`.
580580
====
581581

582582
<<ex_coroaverager3>> provides more context to see `yield from` at work, and <<yield_channel_fig>> identifies the relevant parts of the example.footnote:[The picture in <<yield_channel_fig>> was inspired by a https://www.fluentpython.com/extra/classic-coroutines/images/yield-from.pdf[diagram] by Paul Sokolovsky.]
-221 KB
Binary file not shown.
-884 KB
Binary file not shown.

0 commit comments

Comments
 (0)