Skip to content

CEP: Draft meaning of ~/.conda/environments.txt #126

@jaimergp

Description

@jaimergp

Key points:

  • This is conda-specific, other tools in the ecosystems might not want to use it
  • conda can choose when to register envs (e.g. temporary ones used internally are not registered), but the user cannot disable that (see context for available hidden option)
  • Its location is user-specific, which is controversial (what about multiuser installations? who owns the registry in that case?). Need to clarify the shortcomings and propose strategies forward.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

Status

TODO 📬

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions