Skip to content

feat(python): Document thread pool propagation improvement #15342

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alexander-alderman-webb merged 1 commit into from
Oct 30, 2025
Merged

feat(python): Document thread pool propagation improvement #15342

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/platforms/python/integrations/default-integrations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,9 @@ Reports crashing threads.

This integration also accepts an option `propagate_scope`, which influences the way data is transferred between threads. If set to `True` (default), the current scope will be shared between threads and scope data (such as tags) will be transferred from the parent thread to the child thread.

Next are two code samples that demonstrate what boilerplate you would have to write without `propagate_scope`. This boilerplate is still sometimes necessary if you want to propagate context data into a thread pool, for example.
Context data is automatically propagated in `concurrent.futures` thread pools beginning with version 2.41.0, when `propagate_scope` is `True`.

Next are two code samples that demonstrate what boilerplate you would have to write without `propagate_scope`. This boilerplate is necessary if you want to propagate context data into a thread pool before version 2.41.0, for example.

### Manual propagation

Expand Down
Loading