|
instance = nipype_factory(arg0, base_class=cls, *nargs, **nkwargs) |
|
super().__init__( |
|
definition=definition, |
|
activate_copy=True, |
|
inputs_to_copy=inputs_to_copy, |
|
inputs_to_symlink=inputs_to_symlink, |
|
inputs_to_clean=inputs_to_clean, |
|
use_temp_output_dir=use_temp_output_dir, |
|
*args, |
|
**kwargs, |
|
) |
|
super().__init__( |
|
definition=definition, |
|
activate_copy=False, |
|
use_temp_output_dir=use_temp_output_dir, |
|
*args, |
|
**kwargs, |
|
) |
See flake8-bugbear B026 star-arg-unpacking-after-keyword-arg:
Why is this bad?
In Python, you can use star-argument unpacking to pass a list or tuple of arguments to a function.
Providing a star-argument after a keyword argument can lead to confusing behavior, and is only supported for backwards compatibility.
capsul/capsul/process/process.py
Line 942 in fbec45b
capsul/capsul/process/process.py
Lines 1077 to 1086 in fbec45b
capsul/capsul/process/process.py
Lines 1090 to 1096 in fbec45b
See flake8-bugbear B026 star-arg-unpacking-after-keyword-arg: