pip and uv output should be optionally visible during micromamba environment creation

[rmittal87]

Troubleshooting docs

• [x] My problem is not solved in the Troubleshooting docs

Anaconda default channels

• [x] I do NOT use the Anaconda default channels (pkgs/* etc.)

How did you install Mamba?

Mambaforge or latest Miniforge

Search tried in issue tracker

https://github.com/mamba-org/mamba/pull/3419

Latest version of Mamba

• [x] My problem is not solved with the latest version

Tried in Conda?

I have this problem with Conda as well, without using Mamba

Describe your issue

With micromamba 2.3.0, output from pip and uv subprocesses is now silenced . This makes debugging harder, especially for large or brittle Python dependency sets.

Would it be possible to:

Add a flag like or

Respect an environment variable (e.g., MICROMAMBA_SHOW_HOOK_OUTPUT=1)

so that users can restore the old behavior when needed?

mamba info / micromamba info

Logs

environment.yml

~/.condarc