bpo-40225: Don't raise an exception on normal return from generator.#19473
Conversation
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit cec3fae987bfa8358da66674c2008b1828cdb5a0 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
|
FYI, the current ref leak is a known issue. |
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit cec3fae987bfa8358da66674c2008b1828cdb5a0 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
|
Re-running on buildbots. If the failures are the same as master, then I'll merge. |
|
I don't think this introduces a leak, but the stdout of the refleaks test differs, so I'm going to hold off merging until the buildbots are green. |
cec3fae to
232a0f7
Compare
|
🤖 New build scheduled with the buildbot fleet by @markshannon for commit 232a0f7 🤖 If you want to schedule another build, you need to add the ":hammer: test-with-buildbots" label again. |
|
The windows buildbot failure seems totally unrelated and the buildbot seems unstable, so merging. |
Reducing runtime on the example program in bpo-40225 on my machine from 2.427s to 0.142s. (With a non PGO, LTO build).
https://bugs.python.org/issue40225