1
53%
master: 53%

Ran 05 Apr 2017 09:49PM UTC

Files 90

Run time 5s

Badge

Embed ▾

Committed 05 Apr 2017 09:03PM UTC coverage: 92.515% (+0.002%) from 92.513%

Job # PYTHON=2.7 NUMPY=1.10.4 PANDAS=0.19.0 COVERAGE='true' PARALLEL='false' TEST_IMPORTS='false' XTRATESTARGS=

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

Add constructor plugins to dask.array (#2142)

* Add constructor plugins to dask.array

This adds a `__new__` constructor to the Array class that enables
user-defined plugins to override array construction.

Some comments/concerns:

1.  Using `__new__` is powerful but also dangerous.  Are there other
    alternatives?  This may break other code; for example, this
    inadvertently breaks pickling.
2.  Do we want to apply this to the Base class?  If so then how do we
    want to enable users to define class-specific plugins?  Add them to
    the class as class variables?
3.  Are there better names for `da.constructor_plugins`?

* merge __init__ into __new__

* Use dask.set_options for constructor plugins

* Add __getnewargs__ method

Classes implementing __new__ need to have this to support pickling.
We replace the `_args` method, which did the same thing.

* remove getstate and setstate methods

These are no longer necessar now that we have __getnewargs__

* add __reduce__ to dask.array

* remove getnewargs

* add plugin docs

Coverage Stats

12384 of 13386 relevant lines covered (92.51%)

0.93 hits per line

dask / dask / 5825 / 1
53%
master: 53%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 5825.1 (PYTHON=2.7 NUMPY=1.10.4 PANDAS=0.19.0 COVERAGE='true' PARALLEL='false' TEST_IMPORTS='false' XTRATESTARGS=)

dask / dask / 5825 / 1 53% master: 53%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 5825.1 (PYTHON=2.7 NUMPY=1.10.4 PANDAS=0.19.0 COVERAGE='true' PARALLEL='false' TEST_IMPORTS='false' XTRATESTARGS=)

dask / dask / 5825 / 1
53%
master: 53%

README BADGES
x