mrocklin / dask / 2363

92%

master: 94%

push

travis-ci

Avoid deepcopy in dask.config.set

When using dask.config.set as a context manager we need to be able to
reverse the changes we make.

Before we used to do a `deepcopy` of the previous configuration and
then apply it back when we exited.  This was expensive and broke
whenever the configuration contained anything that wasn't easily
deepcopyable (roughly the same things that aren't pickleable).

Now we record what changes we made, and remove them more surgically.

29 of 29 new or added lines in 1 file covered. (100.0%)

15805 of 17245 relevant lines covered (91.65%)

0.92 hits per line