Skip to content
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

FIX: Require environment variable to use DataLad #8

Merged
merged 3 commits into from
Mar 13, 2019

Conversation

oesteban
Copy link
Member

This PR adds a check on TEMPLATEFLOW_USE_DATALAD (default unset
or false) which needs to evaluate to True in order to use
DataLad.

This fix addresses nipreps/fmriprep#1534.

This PR adds a check on ``TEMPLATEFLOW_USE_DATALAD`` (default unset
or false) which needs to evaluate to ``True`` in order to use
DataLad.

This fix addresses nipreps/fmriprep#1534.
@oesteban oesteban merged commit c2be322 into master Mar 13, 2019
@oesteban oesteban deleted the fix/datalad-default branch March 13, 2019 03:17
Copy link
Contributor

@yarikoptic yarikoptic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for DataLad causing some disturbances (building custom build of libc6 as speaking to see if we could provide git-annex-standalone build which would work on ancient centos boxes). But wouldn't it be worth mentioning this variable somewhere in the docs?


if any(not_fetched):
raise RuntimeError(
"Could not fetch template files: %s" % ', '.join(not_fetched))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

may be the error could include a message about TF_USE_DATALAD (if that one was not set), to instruct users about a possible way to get those files where applicable?

@oesteban
Copy link
Member Author

Hehehe, before adding the variable to the docs, we need to build docs at all (opened #9)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants