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.

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

New environment.yml generation is buggy #12

Open
trevorcampbell opened this issue Aug 31, 2023 · 3 comments · May be fixed by #14
Open

New environment.yml generation is buggy #12

trevorcampbell opened this issue Aug 31, 2023 · 3 comments · May be fixed by #14

Comments

@trevorcampbell
Copy link
Collaborator

trevorcampbell commented Aug 31, 2023

Misses tidyclust and ISLR etc (because it's not installed using mamba)

This may need to be manually updated for now...

(same in py repo)

@trevorcampbell
Copy link
Collaborator Author

trevorcampbell commented Aug 31, 2023

One issue is that tidyclust is not yet available on conda forge. See tidymodels/tidyclust#167

@trevorcampbell
Copy link
Collaborator Author

I wonder if we should ditch the environment.yml file and just have a shell script so that we can do whatever we want and not worry about future compatibility...

If we do this, we should keep the environment file anyway (or maybe we can somehow force conda to print a warning message pointing people to our repo where we have our new shell script....hmmm)

@trevorcampbell
Copy link
Collaborator Author

In order to get conda to print a message when trying to update the environment, you can do something like the following

(note the two dots are important to get conda to fail quickly, otherwise it takes forever searching for a bogus package name)

name: base
dependencies:
  - ". . hello this is a message"

If you run conda env update environment.yml on that file, you will see

(base) jovyan@5d0fe92f9fae:~$ conda env update --file environment.yml 

CondaValueError: invalid package specification: . . hello this is a message

@trevorcampbell trevorcampbell linked a pull request Sep 13, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant