Timeline for What does the "yield" keyword do in Python?
Current License: CC BY-SA 4.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 19 at 20:03 | comment | added | qneill | @bobstein - I posted an answer over there but TBH I'm no VS Code guru. | |
| Feb 2 at 15:27 | comment | added | Bob Stein |
@qneill man I could use some minutia over at this question I just posted about VS Code not getting along with git. How did version control get so messy?
|
|
| Feb 2 at 3:11 | comment | added | qneill |
@BobStein LOL "glazed eyes" I get that a lot as I found myself too steeped in git minutia and learned I really, really needed to crimp the firehose.
|
|
| Feb 16, 2023 at 14:40 | comment | added | Bob Stein | @D-odu if I've earned your compliment, the real people to thank are the many whose eyes have glazed over listening to me. I'll take credit for noticing and trying to avoid that. | |
| Feb 16, 2023 at 12:31 | comment | added | D-odu | I like people like yourself. Explaining things clearly without unnecessary jargon | |
| Jan 4, 2019 at 15:30 | history | edited | Bob Stein | CC BY-SA 4.0 |
minor improvements in clarity, links, naming
|
| Sep 7, 2018 at 17:15 | history | edited | Bob Stein | CC BY-SA 4.0 |
simpler wording
|
| Apr 10, 2018 at 0:37 | history | edited | Bob Stein | CC BY-SA 3.0 |
added 20 characters in body
|
| Apr 8, 2018 at 18:25 | history | edited | Bob Stein | CC BY-SA 3.0 |
deleted 81 characters in body
|
| Sep 23, 2017 at 15:41 | history | edited | Bob Stein | CC BY-SA 3.0 |
code comments highlight changes
|
| Sep 19, 2017 at 1:00 | history | edited | Bob Stein | CC BY-SA 3.0 |
deleted 44 characters in body
|
| May 23, 2017 at 12:18 | history | edited | URL Rewriter Bot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| May 17, 2017 at 12:01 | history | edited | MSeifert | CC BY-SA 3.0 |
use next function instead of next method, the next method was renamed to __next__ in python-3
|
| Dec 30, 2016 at 23:11 | history | edited | Bob Stein | CC BY-SA 3.0 |
Use this simple trick to get multi-use out of a generator function.
|
| Sep 30, 2016 at 11:21 | history | edited | Bob Stein | CC BY-SA 3.0 |
Clarify, "generator" is used in Python 3 docs as a more specific term for the iterator. "Generator function" is therefore unambiguous. Avoiding the term "generator" altogether, which is now ambiguous (some texts use it for the function).
|
| Aug 15, 2016 at 15:53 | history | edited | Bob Stein | CC BY-SA 3.0 |
the_list is a better name then return_list (more noun-like), and other tweaks
|
| Jun 10, 2016 at 18:00 | history | edited | Bob Stein | CC BY-SA 3.0 |
oops sequence has specific meaning in Python too, changing to series
|
| Jun 10, 2016 at 17:51 | history | edited | Bob Stein | CC BY-SA 3.0 |
tie in to double meaning of 'yield'
|
| May 14, 2016 at 17:25 | history | edited | Bob Stein | CC BY-SA 3.0 |
Correct iterator / generator terminology. Calling next(iterator) is Python 2/3 compatible, versus iterator.next() which is Python 2 only, thanks to @Passiday's comment.
|
| May 1, 2016 at 19:26 | history | edited | Bob Stein | CC BY-SA 3.0 |
added 20 characters in body
|
| Apr 22, 2016 at 19:30 | history | edited | Bob Stein | CC BY-SA 3.0 |
More info. Less snark.
|
| Apr 21, 2016 at 22:25 | history | edited | Bob Stein | CC BY-SA 3.0 |
Drawing prime attention to the code, which explains it faster.
|
| Mar 25, 2016 at 13:58 | history | edited | Bob Stein | CC BY-SA 3.0 |
added 93 characters in body
|
| Mar 25, 2016 at 13:28 | history | edited | Bob Stein | CC BY-SA 3.0 |
added 106 characters in body
|
| Mar 25, 2016 at 13:21 | history | answered | Bob Stein | CC BY-SA 3.0 |