This templating engine is an odd artifact at this point and actually wont work anymore unless there happens to be a directory in the user's CWD that matches the currently active environment.
Per searches here on GitHub conda-forge, bioconda, nor Anaconda uses this templating engine anymore.
Uncovered while investigating #5493
Why is this needed?
Less legacy code to wrangle.
What should happen?
Review and remove clearly outdated code from the Jinja templating engine.
Checklist
What is the idea?
Originally added in https://github.com/conda/conda-build/pull/578 (see writeup in https://github.com/conda/conda-build/pull/575) this templating engine would appear to be a precursor to the
conda_build_config.yaml
used today.This templating engine is an odd artifact at this point and actually wont work anymore unless there happens to be a directory in the user's CWD that matches the currently active environment.
Per searches here on GitHub
conda-forge
,bioconda
, nor Anaconda uses this templating engine anymore.Uncovered while investigating #5493
Why is this needed?
Less legacy code to wrangle.
What should happen?
Review and remove clearly outdated code from the Jinja templating engine.
Additional Context
No response