ENH: ICA_AROMA: make current working directory default output directory

[jdkent]

Changes proposed in this pull request

• Make the default output directory the current working directory so you don't have to specify an out_dir, which I believe makes ICA_AROMA more Node friendly.

[jdkent]

I was a little hasty getting this up. Please ignore until I fix it. Fixed.

[codecov-io]

Codecov Report

❗ No coverage uploaded for pull request base (master@9d63943). Click here to learn what that means.
The diff coverage is 25%.

@@            Coverage Diff            @@
##             master    #2056   +/-   ##
=========================================
  Coverage          ?   72.16%           
=========================================
  Files             ?     1137           
  Lines             ?    57194           
  Branches          ?     8194           
=========================================
  Hits              ?    41276           
  Misses            ?    14629           
  Partials          ?     1289

Flag	Coverage Δ
#smoketests	72.16% <25%> (?)
#unittests	69.78% <25%> (?)

Impacted Files	Coverage Δ
nipype/interfaces/fsl/tests/test_auto_ICA_AROMA.py	85.71% <ø> (ø)
nipype/interfaces/fsl/ICA_AROMA.py	68.42% <25%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9d63943...48fcf86. Read the comment docs.

[satra]

@jdkent - could you please resolve conflicts with master? relative imports should always be used in nipype - we stopped being careful during review.

[jdkent]

@satra: you've probably answered this a thousand times, but why use relative versus absolute imports? Not that I abide by PEP for everything, but PEP 328 wants to make absolute imports standard. Does it have to do with making sure we are importing the right packages if we have multiple versions of nipype installed? Sorry for badgering, but I am curious.

[effigies]

@jdkent I think you may be misreading PEP 328, which is about interpretation of import statements. Pre-PEP328, import x would look for x in the local package, i.e. all imports were assumed relative. PEP328 moved to implicit absolute imports and explicit relative imports.

But yes, using relative imports does ensure that we use a package-local version, rather than one found in the PYTHONPATH. (It also helps with including nipype as a submodule in other packages.)

Incidentally, @oesteban it looks like from __future__ import absolute_import was only necessary pre-2.6? Nipype doesn't support before 2.7, so that's probably why all the missing absolute_import requirements haven't had any effect.

[jdkent]

I think I need the isdefined module for this line to run, please let me know if I'm mistaken.

[effigies]

Good catch. Please add isdefined to the from ..base import line.