Bugfix in ImageWrapper.calcExpansion - could not handle slice outside of
coverage, but overlapping with some dimensions.

Initial support in Image class for data editing.

regions are specified with nan (which can't be represented as uint32).

function should not be here.

documentation.

tests because i'm impatient.

into a separate method, as it will probably come in handy for write
support.

offers a more fine-grained result. Adjusted sliceCovered - function it
doesn't need to know the image shape. updateDataRangeOnRead is no longer
memoized - slice coverage is checked before it is called, so it
shouldn't need to be memoized.

amount of time to run.

also skips __getitem__ coverage update if the full image data range has
been calculated.

imagewrapper module.

between expansions.

no sense, I know.

data is read. But the dataRange property will return cal_min/cal_max
if no data has been read. Some documentation added too.

comparisons to None now testing for isnan.

ImageWrapper now maintains separate coverages for each volume (in a 4D
image, or slice in a 3D image), and adjusts them individually. Lots of
crazy code which seems to work ok, but has not been tested or
documented. Most of the complex stuff has been turned into standalone
functions, so can be unit-tested.

arg. When a Notifier listener is registered, it can be specified to run
on async.idle (to avoid threading issues).

As an aside, I have just realised that there is a naming collision
between Notifier.notify and HasProperties.notify, for anything which
sub-classes both. I don't think anything does, but this will probably
bite me in the future.

files. Log messages added to memoize functions.

HasProperties type).

initialisation. Image.name property turned into a regular (writeable)
attribute.

changes. Bugfix in Image.__getitem__ - was potentially returning data
with trailing dimensions of size 1.

function.