You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updated iter_bucket to use concurrent futures. (#368)
* Updated iter_bucket to use concurrent futures.
This commit addresses issue #340.
AWS Lambda environments do not support multiprocessing.Queue or
multiprocessing.Pool, which are used by iter_bucket to optimize the
pulling of files from s3.
Solution: Switch to using concurrent.futures.ThreadPoolExecutor instead.
This still optimizes the pulling of files from s3 without using new
processes.
* disable test_old when mocks are disabled
* favor multiprocessing over concurrent.futures
* make imap_unordered return an iterator instead of a list
* skip tests when their respective features are unavailable
* Revert "disable test_old when mocks are disabled"
This reverts commit 6506562.
* tweak imap_unordered
* remove tests_require pins
Co-authored-by: Michael Penkov <m@penkov.dev>
0 commit comments