Loky

Latest version: v3.4.1

Safety actively analyzes 619159 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 7

3.5.0

3.4.1

- Fix compatibility with python3.7, which does not define
a `_MAX_WINDOWS_WORKERS` constant. (408)

3.4.0

- Fix exception `__cause__` not being propagated with
`tblib.pickling_support.install()`. (255).

- Fix handling of CPU affinity by using `psutil`'s `cpu_affinity` on platforms
that do not implement `os.sched_getaffinity`, such as PyPy. (381).

- Make the executor's gc process more thread-safe, in particular for PyPy,
where the gc calls can be run in any thread. (384).

- Fix crash when using `max_workers > 61` on Windows. Loky will no longer
attempt to use more than 61 workers on that platform (or 60 depending on the
Python version). (390).

- Fix loky compat with python 3.11 for nested calls. (394).

- Adapt the cooldown strategy when shutingdown an executor with full
`call_queue`. This should accelerate the time taken to shutdown
in general, in particular on overloaded machines. (399).

3.3.0

- Fix worker management logic in `get_reusable_executor` to ensure
the number of started worker process actually correspond to `max_workers`
when existing process concurrently time out (370).

3.2.0

- Fix leaked processes and deadlock when the Python interpreter exits
after a using nested calls to `get_reusable_executor` (363).

- Fix an exception in the SemLock finalizer when the semaphore has been
concurrently unlinked (366).

3.1.0

- Fix loky.cpu_count() to properly detect the number of allowed CPUs based on
the /sys/fs/cgroup/cpu.max file on newest Linux versions with cgroup v2.
Fall-back to the /sys/fs/cgroup/cpu/cpu.cfs_quota_us file to keep on
supporting Linux versions that use cgroup v1 (355 and 358).

- Fix an exception that could be raised in an auxiliary thread when
garbage collecting an executor instance when shutting down the
the Python interpreter (311).

- Make `shutdown(kill_workers=True)` consistently use the SIGKILL
signal on POSIX. Previously a mix of SIGKILL and SIGTERM was issued
and could deadlock the shutdown process (348 and 357).

- Big code clean-up to drop support for older Python versions.
Python 3.7 or later is now required. (304)

Page 1 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.