Skip to content
This repository has been archived by the owner on Jan 30, 2019. It is now read-only.

conda env export has no-builds as default #119

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

malev
Copy link
Contributor

@malev malev commented Jul 9, 2015

  • --no-builds deprecated
  • --with-bilds new flag
  • conda env attach adds environment without builds name

@groutr
Copy link
Collaborator

groutr commented Jul 15, 2015

I think there is a better solution than stripping build numbers. It would be a whole more useful if conda env matched to varying levels of strictness when replicating an environment. The user could control whether conda-env matches just the package name, package name + version, or package name + version + build number.

This would mean that environment.yml should include build numbers. I think it is better to adjust the interpretation of the these values rather than strip them out entirely.

Thoughts?

@malev
Copy link
Contributor Author

malev commented Jul 21, 2015

on hold for now

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants