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

environment.yaml not detected due to "yaml" extension instead of "yml" #99

Closed
l-salewski opened this issue Jul 28, 2021 · 1 comment · Fixed by #100
Closed

environment.yaml not detected due to "yaml" extension instead of "yml" #99

l-salewski opened this issue Jul 28, 2021 · 1 comment · Fixed by #100

Comments

@l-salewski
Copy link

I just encountered this error FileNotFoundError: environment.yml not found which I was able to fix by renaming my environment.yaml file to environment.yml. Alternatively using the -f environment.yaml option also works.

The internet seems to be split on which version is the correct extension, but ignoring this discussion it would be really nice to just support both yaml and yml out of the box.
@mariusvniekerk mariusvniekerk mentioned this issue Aug 2, 2021
Merged
@l-salewski
Copy link
Author

Thanks a lot!

riccardoporreca added a commit to riccardoporreca/conda-lock that referenced this issue Aug 10, 2022
@riccardoporreca
Fix behavior and checks for unspecified source files
3318dd4 
* Resolves conda#231, reviewing and extending the logic for supporting .yaml extension (conda#99).
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
No milestone
Development

Successfully merging a pull request may close this issue.

Add support for automatically support environment.yaml mariusvniekerk/conda-lock
1 participant
@l-salewski