Skip to content

Replace shard stack with imports from conda #908

@danyeaw

Description

@danyeaw

Checklist

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

What is the idea?

After conda is updated with sharded repodata in conda.gateways.repodata.shards, conda-libmamba-solver stops hosting its own shards* modules and imports and calls conda’s gateway from index/plugin wiring instead.

Why is this needed?

Prevents two implementations and keeps libmamba aligned with the canonical client owned by conda.

What should happen?

  • Local shard fetch/cache/subset logic is removed
  • Implement plugin API for shards only

Additional Context

Depends on conda/conda#15906.

Metadata

Metadata

Assignees

No one assigned

    Labels

    type::featurerequest for a new feature or capability

    Type

    No type

    Projects

    Status

    Sorting ⚙️

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions