Skip to content

Make terminal_output not mandatory (since it has a silent default). #1070

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 18, 2015

Conversation

chrisgorgo
Copy link
Member

This will improve the clarity of documentation.

@chrisgorgo chrisgorgo force-pushed the enh/terminal_output branch from 5e32bde to 49a2134 Compare March 18, 2015 18:35
@coveralls
Copy link

Coverage Status

Coverage decreased (-2.84%) to 67.91% when pulling 49a2134 on chrisfilo:enh/terminal_output into 4bd4ed9 on nipy:master.

@chrisgorgo
Copy link
Member Author

The decreased coveraged is due to this:

$ make specs
Checking specs and autogenerating spec tests
python tools/checkspecs.py
150318-11:57:23,977 workflow DEBUG:
     networkx 1.4 dev or higher detected
ErrorMap has nonautotest
Overlap has nonautotest

@satra
Copy link
Member

satra commented Mar 18, 2015

ah now i remember why the default was essential - we need to ensure that any interface that relies on terminal output (e.g., fslstats) always sets this to stream or file.

it also makes me think that it might be nice for the command line class to have a terminal_output output spec as well (we don't have to make the change here, but would be nice to add during the sprint). that way people can sink those as well. we do capture it in the report (in some cases) and in the prov. so it may not be complete necessary.

otherwise this looks good. can you update the CHANGES?

@chrisgorgo
Copy link
Member Author

On Wed, Mar 18, 2015 at 12:15 PM, Satrajit Ghosh notifications@github.com
wrote:

ah now i remember why the default was essential - we need to ensure that
any interface that relies on terminal output (e.g., fslstats) always sets
this to stream or file.

That could be easily done by overriding this in the InputSpec. Like here:

terminal_output = traits.Enum('allatonce',

it also makes me think that it might be nice for the command line class
to have a terminal_output output spec as well (we don't have to make the
change here, but would be nice to add during the sprint). that way people
can sink those as well. we do capture it in the report (in some cases) and
in the prov. so it may not be complete necessary.

otherwise this looks good. can you update the CHANGES?

Happy to do this, but isn't it too small?

@satra
Copy link
Member

satra commented Mar 18, 2015

no - this is a pseudo API change, so i don't think it hurts to be included. i know practically it doesn't affect anyone really.

chrisgorgo added a commit that referenced this pull request Mar 18, 2015
Make terminal_output not mandatory (since it has a silent default).
@chrisgorgo chrisgorgo merged commit 5ec56d6 into nipy:master Mar 18, 2015
@chrisgorgo chrisgorgo deleted the enh/terminal_output branch March 18, 2015 20:24
@chrisgorgo chrisgorgo restored the enh/terminal_output branch March 18, 2015 22:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants