Closed
Description
Summary
When using CLI utility to open a crash file, if it was generated in a different nipype version, it may show strange/unrelated errors.
Actual behavior
Exceptions from different reasons are shown when a crash file is opened with a different nipype version than the one that generated the crash.
Expected behavior
Better deal with this version difference, at least showing that there is a problem to the user.
How to replicate the behavior
Try to open a crash file from a different nipype version, especially when the classes within the crash were changed.
Script/Workflow details
N/A
Platform details:
Please paste the output of: python -c "import nipype; print(nipype.get_info()); print(nipype.__version__)"
{
'pkg_path': '/home/anibalsolon/Documents/nipype/anibalsolon/nipype',
'commit_source': 'repository',
'commit_hash': 'b5d79b4',
'nipype_version': '1.1.0-dev+gb5d79b4',
'sys_version': '3.6.4 |Anaconda custom (64-bit)| (default, Jan 16 2018, 18:10:19) \n[GCC 7.2.0]',
'sys_executable': '/opt/anaconda3/bin/python',
'sys_platform': 'linux',
'numpy_version': '1.14.0',
'scipy_version': '1.0.0',
'networkx_version': '2.1',
'nibabel_version': '2.2.1',
'traits_version': '4.6.0'
}
1.1.0-dev+gb5d79b4```
### Execution environment
Choose one
- My python environment outside container
Metadata
Metadata
Assignees
Labels
No labels