You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I added the support for the placeholder in containers-run with #227. This means it will get resolved before run can see it, and it will enter the run record in resolved form.
This is bad, because this resolved form is as non-portable as the previous setup, if not more.
This change must be amended, the resolution must be performed in run, and here we need to use the placeholder in its escaped form: {{python}}.
A viable approach might be to define datalad.run.substitutions.python=sys.executable
The text was updated successfully, but these errors were encountered:
This causes worse portability issues than the previous approach
of storing `python(.exe)`.
Instead pass the placeholder on to `datalad run`.
This would now error with
```
command has an unrecognized placeholder: 'python'
```
and requires a further intervention. Three options:
- have datalad-core define
`datalad.run.substitutions.python=sys.executable`
- wait for datalad#244
and use `register_config()` to have datalad-container define it
- have datalad-container define it at `containers-run` runtime by
patching the configuration for the execution time (would have `rerun`
fail still)
- add the configuration item to the committed dataset config
Closesdatalad#249
mih
added a commit
to mih/datalad-container
that referenced
this issue
Oct 12, 2023
I added the support for the placeholder in
containers-run
with #227. This means it will get resolved beforerun
can see it, and it will enter the run record in resolved form.This is bad, because this resolved form is as non-portable as the previous setup, if not more.
This change must be amended, the resolution must be performed in
run
, and here we need to use the placeholder in its escaped form:{{python}}
.A viable approach might be to define
datalad.run.substitutions.python=sys.executable
The text was updated successfully, but these errors were encountered: