Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make env_specs optional #222

Closed
mcg1969 opened this issue Aug 7, 2019 · 1 comment
Closed

Make env_specs optional #222

mcg1969 opened this issue Aug 7, 2019 · 1 comment
Milestone
0.8.4

Comments

@mcg1969
Copy link
Collaborator

mcg1969 commented Aug 7, 2019

We should support an operational mode where env_specs is not required. If the user is content with a single environment named default whose packages and channels are specified in the global packages and channels sections, that should be sufficient.

Optionally, we could add an env_name keyword that renames the default environment in that case, if supplied.
@mcg1969 mcg1969 added this to the 0.8.4 milestone Aug 7, 2019
@mcg1969
Copy link
Collaborator Author

mcg1969 commented Oct 24, 2019

Fixed by #232

@mcg1969 mcg1969 closed this as completed Oct 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.8.4
Development

No branches or pull requests
1 participant
@mcg1969