| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Per the bot, please add a news entry, and please also update the "What's New in Python 3.15" document.
Sorry, something went wrong.
|
Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool. If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead. |
Sorry, something went wrong.
There was a problem hiding this comment.
Just down to docs nitpicks for me. The rest looks good.
Sorry, something went wrong.
|
There was a fun issue where the precommit merge conflict checker thought that a perfectly legitimate string was a problem: check for merge conflicts................................................Failed Doc/whatsnew/3.15.rst:680: Merge conflict string '=======' found I removed one of the = and it was happy again :) (and then added it back after) |
Sorry, something went wrong.
|
Thanks @ZeroIntensity, appreciate all the feedback! |
Sorry, something went wrong.
There was a problem hiding this comment.
Thanks, this looks good to me. I'll wait for @gpshead as the multiprocessing expert to decide on the weird triple-quotes in the message.
Sorry, something went wrong.
|
Hmm, something seems to be causing the tests to hang. |
Sorry, something went wrong.
|
Hi @ZeroIntensity and @gpshead! Tests are passing, let me know if there are any other changes you'd like me to make, or if this is good to go. |
Sorry, something went wrong.
|
@AA-Turner @ZeroIntensity @gpshead thanks for all the feedback thus far! Let me know if there's anything else you'd like me to change here. |
Sorry, something went wrong.
…tion report which child process terminated (pythonGH-139486) Report which process terminated as cause of BPE
| Back | FazBrowse Home | New Git URL |
See #139462 for more context.
Short summary: prior to this change, if a child process segfaulted when running in a concurrent.futures.ProcessPoolExecutor, the user would get a BrokenProcessPool exception with no information about which child process terminated or why.
In order to improve the debugging experience, this change attempts to report which child process terminated and with what exit code. For instance, if I have a worker process that segfaults, I'll now see something like: