We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
interface.utils.eval_results
interface(.base)
There is pretty much no Interface implementation without it, just like with build_doc. IMHO both pieces should live in the same place.
Interface
build_doc
This would make the common
from datalad.interface.base import ( Interface, build_doc, ) from datalad.interface.utils import ( eval_results, )
just be
from datalad.interface.base import ( Interface, build_doc, eval_results, )
an argument could be made to consolidate all (more or less strictly) required pieces in datalad.interface. Looking like this:
datalad.interface
from datalad.interface.base import ( Interface, Parameter, build_doc, datasetmethod, eval_results, )
The text was updated successfully, but these errors were encountered:
MNT: Move interface.utils.eval_results to interface(.base)
633f296
This is solely an internal code move. Fixes datalad#6694
done in #7170
Sorry, something went wrong.
Issue fixed in 0.18.0
0.18.0
Successfully merging a pull request may close this issue.
There is pretty much no
Interface
implementation without it, just like withbuild_doc
. IMHO both pieces should live in the same place.This would make the common
just be
an argument could be made to consolidate all (more or less strictly) required pieces in
datalad.interface
. Looking like this:The text was updated successfully, but these errors were encountered: