Closed
Description
Summary
It would be nice to be able to import nipype without having to decide between disabling etelemetry and triggering output to stdout.
> fitlins --version
190925-23:25:59,835 nipype.utils WARNING:
Could not check for version updates:
Connection to server could not be made
190925-23:25:59,836 nipype.utils INFO:
Running nipype version 1.2.3 (latest: Unknown)
fitlins v0.5.1+6.g4606e4f
I can go ahead and work to delay imports so that running --help
or --version
never hits import 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
Metadata
Metadata
Assignees
Labels
No labels