BF: h5save to deal with '' as currentdir
RF: Consolidate attribute assigning in Searchlight's result_fx

With different result_fx implementations that shape and content of
attributes can be totally different, so all this should consistent
with the actual result_fx
ENH: Extend pass_attr feature to support additional use cases

Like:
- renaming
- axes swapping
- explicit target attribute collections

fully backward compatible
RF: Split _postcall in Measures

This is necessary to allow for picking up the 'null_prob' CA in Node's
pass_attr facility.
DOC: Add a note on workshops
NF: results_postproc_fx for Searchlight

To facilitate parallel postprocessing of the blocks of results to
please Swaroop
Merge remote-tracking branch 'gh-hanke/master'

* gh-hanke/master:
  RF: Split _postcall in Measures
  ENH: Extend pass_attr feature to support additional use cases
  RF: Consolidate attribute assigning in Searchlight's result_fx

Conflicts:
	mvpa2/tests/test_datameasure.py
RF: just for consistency move michael's test inside the suite
BF: fixing up our test for cherry-picked changes from Michael
BF: in _repr_attrs do not print repr of methods. Close #122

It is a rare case but we do not have any other machinery to prevent
going into infinite recursion for those cases where bound methods
also given as parameters (callable)s.  Thus now it would only print
class where this method was bound.  If it is necessary to discover
the actual instance -- enable ID_IN_REPR debug variable
TST: use @with_tempfile to avoid leaving junk around
TST: use @with_tempfile in surfing tests

(Attn: @nno)
ENH: provide debug output, compare reconstruction against original, allow to pass original betas

not sure if that is my bug or what but even if provided original betas and hrf estimates go quite far away
from original ground truth
removed demeaning and still results in bloated betas in noisy cases

More: https://github.com/fabianp/hrf_estimation/issues/4
Merge branch 'master' of github.com:swaroopgj/PyMVPA

Conflicts:
	mvpa2/base/hdf5.py
ENH: simple_hrf_dataset -- can accept pre-crafted HRF array
Added a test case to test_hdf5 that fails to load an empty array object
BF: h5load(ing) an empty array from h5save(d) file results in ZeroDivisionError.
BF: Modified the test to handle zero-sized arrays
ENH: hrf_estimation -- tollerate arbitrary offset/baseline, more testing etc