Skip to content
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

Jump to bottom

Improve documentation for multiprocessing/threading #3831

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

Improve documentation for multiprocessing/threading #3831

Show file tree
Hide file tree
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: 4 additions & 0 deletions docs/source/guide/clients.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,3 +156,7 @@ General Example
futures = [executor.submit(do_s3_task, s3_client, task) for task in my_tasks]

.. _Botocore Events: https://botocore.amazonaws.com/v1/documentation/api/latest/topics/events.html

.. note::

Note that `boto3.client` uses a single, shared session for all calls. This can lead to concurrency issues unexpectedly when done across parallelization primitives. We recommend managing your own session(s) with concurrent code.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

'for all api calls'

4 changes: 4 additions & 0 deletions docs/source/guide/session.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,3 +79,7 @@ to create a new ``Session`` object for each thread or process::
s3 = session.resource('s3')

# Put your thread-safe code here

.. note::

Note that `boto3.client` uses a single, shared session for all calls. This can lead to concurrency issues unexpectedly when done across parallelization primitives. We recommend managing your own session(s) with concurrent code.