Joblib

Latest version: v1.4.2

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

Scan your dependencies

Page 6 of 11

0.9.3

Not secure
-------------

Olivier Grisel

Revert back to the ``fork`` start method (instead of
``forkserver``) as the latter was found to cause crashes in
interactive Python sessions.

0.9.2

Not secure
-------------

Loïc Estève

Joblib hashing now uses the default pickle protocol (2 for Python
2 and 3 for Python 3). This makes it very unlikely to get the same
hash for a given object under Python 2 and Python 3.

In particular, for Python 3 users, this means that the output of
joblib.hash changes when switching from joblib 0.8.4 to 0.9.2 . We
strive to ensure that the output of joblib.hash does not change
needlessly in future versions of joblib but this is not officially
guaranteed.

Loïc Estève

Joblib pickles generated with Python 2 can not be loaded with
Python 3 and the same applies for joblib pickles generated with
Python 3 and loaded with Python 2.

During the beta period 0.9.0b2 to 0.9.0b4, we experimented with
a joblib serialization that aimed to make pickles serialized with
Python 3 loadable under Python 2. Unfortunately this serialization
strategy proved to be too fragile as far as the long-term
maintenance was concerned (For example see
https://github.com/joblib/joblib/pull/243). That means that joblib
pickles generated with joblib 0.9.0bN can not be loaded under
joblib 0.9.2. Joblib beta testers, who are the only ones likely to
be affected by this, are advised to delete their joblib cache when
they upgrade from 0.9.0bN to 0.9.2.

Arthur Mensch

Fixed a bug with ``joblib.hash`` that used to return unstable values for
strings and numpy.dtype instances depending on interning states.

Olivier Grisel

Make joblib use the 'forkserver' start method by default under Python 3.4+
to avoid causing crash with 3rd party libraries (such as Apple vecLib /
Accelerate or the GCC OpenMP runtime) that use an internal thread pool that
is not reinitialized when a ``fork`` system call happens.

Olivier Grisel

New context manager based API (``with`` block) to re-use
the same pool of workers across consecutive parallel calls.

Vlad Niculae and Olivier Grisel

Automated batching of fast tasks into longer running jobs to
hide multiprocessing dispatching overhead when possible.

Olivier Grisel

FIX make it possible to call ``joblib.load(filename, mmap_mode='r')``
on pickled objects that include a mix of arrays of both
memory memmapable dtypes and object dtype.

0.8.4

Not secure
-------------

2014-11-20
Olivier Grisel

OPTIM use the C-optimized pickler under Python 3

This makes it possible to efficiently process parallel jobs that deal with
numerous Python objects such as large dictionaries.

0.8.3

Not secure
-------------

2014-08-19
Olivier Grisel

FIX disable memmapping for object arrays

2014-08-07
Lars Buitinck

MAINT NumPy 1.10-safe version comparisons


2014-07-11
Olivier Grisel

FIX 146: Heisen test failure caused by thread-unsafe Python lists

This fix uses a queue.Queue datastructure in the failing test. This
datastructure is thread-safe thanks to an internal Lock. This Lock instance
not picklable hence cause the picklability check of delayed to check fail.

When using the threading backend, picklability is no longer required, hence
this PRs give the user the ability to disable it on a case by case basis.

0.8.2

Not secure
-------------

2014-06-30
Olivier Grisel

BUG: use mmap_mode='r' by default in Parallel and MemmappingPool

The former default of mmap_mode='c' (copy-on-write) caused
problematic use of the paging file under Windows.

2014-06-27
Olivier Grisel

BUG: fix usage of the /dev/shm folder under Linux

0.8.1

Not secure
-------------

2014-05-29
Gael Varoquaux

BUG: fix crash with high verbosity

Page 6 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.