-
Notifications
You must be signed in to change notification settings - Fork 16
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
Possible to export pip-packages? #75
Comments
For now, you could do something like this: - name: setup micromamba and solve environment
uses: mamba-org/setup-micromamba@v1
with:
environment-file: environment.yml
environment-name: ${{ runner.os }}
- name: export environment created with micromamba using conda
run: |
conda env export -p "${MAMBA_ROOT_PREFIX}/envs/${{ runner.os }}" > ./environments/${{ runner.os }}_solved_with_pip.yml Btw |
Thanks! Just as a sanity check: 1.) If one wants to output a 2.) However, if one wants to output a spec file with the exact package URLs, neither |
Yes, seems right 👍🏻 |
I am using
setup-micromamba@v1
to create environments and would like to export them as text files, either withmicromamba env export --name ... > file.yml
orconda list --explicit > file.txt
. However, I noticed that pip-packages are not included in the exported text files. Is this behavior normal?Here's an example repo where I use the workflow to create an environment based on the input file
environment.yml
, export it to text files and then push it back to the repo (the two files with_solved
as suffixes).The text was updated successfully, but these errors were encountered: