GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||
GeezerVison is showing github.com — gh-159964: Propagate contextvars to ThreadPoolExecutor tasks by methatp0 · Pull Request #160024 · python/cpython Conversation
|
|
The following commit authors need to sign the Contributor License Agreement: |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
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 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
8731f40 to
526dfe8
Compare
Documentation build overview
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Thanks for the patch. I was planning to work on this issue, and I’ll take it from here. The proposed change fixes the reproducer, but unconditional context propagation also changes downstream behavior. I want to think about compatibility questions and performance before settling on an implementation. I’m closing this PR to avoid parallel work; I’ll follow up on the issue. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
ThreadPoolExecutor tasks see the context of whichever submit() call started their worker thread
There was an error while loading. Please reload this page.