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

conda env create -n ENVNAME --file should support json files #12942

Open
2 tasks done
swaldhoer opened this issue Jul 27, 2023 · 1 comment · May be fixed by #13745
Open
2 tasks done

conda env create -n ENVNAME --file should support json files #12942

swaldhoer opened this issue Jul 27, 2023 · 1 comment · May be fixed by #13745
Labels
pending::discussion contains some ongoing discussion that needs to be resolved prior to proceeding source::community catch-all for issues filed by community members type::feature request for a new feature or capability

Comments

@swaldhoer
Copy link

Checklist

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

What is the idea?

conda currently only supports creating new environments from yaml files, i.e.,

conda env create -n ENVNAME --file bla.yml

It would be good to be able to also create new environments from json files:

conda env create -n ENVNAME --file bla.json

Why is this needed?

For conda and the enviroment it lives in, this does not make a difference, whether the enviroment is specfified in yaml or json. However, in a standard CPython installation, there is no yaml support, but only json. In order to be able to work with environment files in standard CPython it would be good, if the enviroment files would also available and usable in json.

conda already support json export (conda env export --json)

Of course one could ducplicate the enviroment and also create both formats, but this is error prone and a single source of truth is the better solution.

What should happen?

conda env create -n ENVNAME --file should accept json files.

Additional Context

No response
@swaldhoer swaldhoer added the type::feature request for a new feature or capability label Jul 27, 2023
@travishathaway travishathaway added the source::community catch-all for issues filed by community members label Jul 28, 2023
@travishathaway
Copy link
Contributor

travishathaway commented Jul 28, 2023 •
edited

Hi @swaldhoer,

Thanks for submitting this feature request. I think this is a very reasonable ask, and it may not even be that hard to implement. I will leave this issue open so that others can discuss.

@travishathaway travishathaway added the pending::discussion contains some ongoing discussion that needs to be resolved prior to proceeding label Jul 28, 2023
swaldhoer added a commit to swaldhoer/conda that referenced this issue Mar 29, 2024
@swaldhoer
Add new entry for conda#12942
fe4f252
@swaldhoer swaldhoer linked a pull request Mar 29, 2024 that will close this issue
Open
3 tasks
swaldhoer added a commit to swaldhoer/conda that referenced this issue Mar 29, 2024
@swaldhoer
Merge branch 'condagh-12942' of https://github.com/swaldhoer/conda into
36a9581 
condagh-12942
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
pending::discussion contains some ongoing discussion that needs to be resolved prior to proceeding source::community catch-all for issues filed by community members type::feature request for a new feature or capability
Projects
🧭 Planning
Status: 🆕 New
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for conda env create -f environment.json swaldhoer/conda
2 participants
@travishathaway @swaldhoer