conda export does not export pip as a dependency of conda and throws syntax error with Windows runner

[JohannesWiesner]

I am using mamba-org/setup-micromamba@v1 to solve an environment using an input .yml file and then export the solved environment using:

conda env export -p "${MAMBA_ROOT_PREFIX}/envs/test" | grep -v "^prefix: " > test_solved.yml (see this link)

When I use the ubuntu-latest runner, everything works fine, but when I use the windows-latest image, two strange things happen:

1.) Normally, pip itself should appear as a dependency itself in the conda section before the pip packages get listed. This does not happen.
2.) When inspecting the exported .yml file there seems to be a syntax error. The first package under the pip: section looks like this:

  - pip:
      - ==9.2.6

I created a minimal repo to reproduce this error: https://github.com/JohannesWiesner/test_push_yml/tree/main

[jonashaag]

Can you try to reproduce this locally (without GHA) with a recent version of Micromamba and Conda?

[JohannesWiesner]

I asked a colleague who has Windows installed to do it. Will come back to you with the results. In the meantime I also changed the input .yml file from this to this:

channels:
  - conda-forge
dependencies:
  - python
  - scikit-learn
  - pip
  - pip:
    - xmltodict

Here also something strange is happening. Pip lists itself as a dependency:

  - pip:
      - brotli==1.0.9
      - certifi==2023.5.7
      - charset-normalizer==3.2.0
      - idna==3.4
      - joblib==1.3.0
      - numpy==1.25.1
      - packaging==23.1
      - pip==23.2

[JohannesWiesner]

@jonashaag : @Engrammae could reproduce the errors locally on his Windows machine. Might then be a mamba/micromamba issue?

[jonashaag]

Yes!

[jonashaag]

I transfered the issue to the Mamba repo