Skip to content

Remove broken $CONDA_DEFAULT_ENV templating engine #5494

@kenodegard

Description

@kenodegard

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

Originally added in #578 (see writeup in #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

Metadata

Metadata

Assignees

No one assigned

    Labels

    in-progressissue is actively being worked onsource::anacondacreated by members of Anaconda, Inc.stale[bot] marked as stale due to inactivitytype::featurerequest for a new feature or capabilitytype::tech-debtidentifies or resolves some technical debt

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions