-
Notifications
You must be signed in to change notification settings - Fork 533
etelemetry pollutes stdout by default #3053
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
Comments
@effigies - i agree - this is something i was trying to help with by encapsulating the etelemetry into a check in #3049 so we can definitely move the check as a one time check in either the alternative is to make this happen with the first run call on an interface or workflow. that may be a better situation. |
I think you can do it in >>> import nipype
>>> _ = nipype.pipeline.engine.base.EngineBase(name="test")
Initialized What if we decorate class EngineBase(object):
"""Defines common attributes and functions for workflows and nodes."""
def __init__(self, name=None, base_dir=None):
""" Initialize base parameters of a workflow or node
Parameters
----------
name : string (mandatory)
Name of this node. Name must be alphanumeric and not contain any
special characters (e.g., '.', '@').
base_dir : string
base output directory (will be hashed before creations)
default=None, which results in the use of mkdtemp
"""
self._hierarchy = None
self.name = name
self._id = self.name # for compatibility with node expansion using iterables
self.base_dir = base_dir
self.config = deepcopy(config._sections)
if self.config.getboolean('execution', 'check_version'):
check_version() |
I was about to report this. Thanks! |
Proposed satra#30. Not sure where we want to continue this discussion, so now all three threads are linked. |
Fixed in #3049 |
Summary
It would be nice to be able to import nipype without having to decide between disabling etelemetry and triggering output to stdout.
I can go ahead and work to delay imports so that running
--help
or--version
never hitsimport nipype
, but that seems a bit much to ask of most tools.Perhaps we could make it trigger on something like on the first instantiation of a workflow or interface, instead of import?
Execution environment
circleci/python:latest
The text was updated successfully, but these errors were encountered: