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

mamba uninstall not recognized as alias to mamba remove #3648

Closed
3 tasks done
fperez opened this issue Dec 2, 2024 · 2 comments · Fixed by #3650
Closed
3 tasks done

mamba uninstall not recognized as alias to mamba remove #3648

fperez opened this issue Dec 2, 2024 · 2 comments · Fixed by #3650

Comments

@fperez
Copy link

fperez commented Dec 2, 2024

Troubleshooting docs

  • My problem is not solved in the Troubleshooting docs

Anaconda default channels

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

How did you install Mamba?

Mambaforge or latest Miniforge

Search tried in issue tracker

uninstall

Latest version of Mamba

  • My problem is not solved with the latest version

Tried in Conda?

I do not have this problem with Conda, just with Mamba

Describe your issue

mamba uninstall is supposed to be an alias for mamba remove:

image

But it's not recognized as such by the latest version (2.0.4):

(base) (main)longs[setup]> mamba --version
2.0.4
(base) (main)longs[setup]> mamba uninstall jupytext
The following arguments were not expected: jupytext uninstall
Run with --help for more information.
(base) (main)longs[setup]> mamba remove jupytext

[... WORKS FINE...]

This used to work until pretty recently, as that's always been the command I used. While remove is nice and maybe shorter, since many other package managers use uninstall as their default command, it's burned in my muscle memory. I think compatibility with this alias should be maintained, not only to avoid breaking user muscle memory, but more importantly, potential automated scripts and pipelines that rely on it.

mamba info / micromamba info

(base) (main)longs[setup]> mamba info

       libmamba version : 2.0.4
          mamba version : 2.0.4
           curl version : libcurl/8.10.1 OpenSSL/3.4.0 (SecureTransport) zlib/1.3.1 zstd/1.5.6 libssh2/1.11.1 nghttp2/1.64.0
     libarchive version : libarchive 3.7.7 zlib/1.3.1 liblzma/5.2.6 bz2lib/1.0.8 liblz4/1.9.3 libzstd/1.5.6
       envs directories : /Users/fperez/local/conda/envs
          package cache : /Users/fperez/local/conda/pkgs
                          /Users/fperez/.mamba/pkgs
            environment : base (active)
           env location : /Users/fperez/local/conda
      user config files : /Users/fperez/.mambarc
 populated config files : /Users/fperez/.condarc
                          /Users/fperez/local/conda/.condarc
       virtual packages : __unix=0=0
                          __osx=15.1.1=0
                          __archspec=1=x86_64_v3
               channels : https://conda.anaconda.org/conda-forge/noarch
                          https://conda.anaconda.org/conda-forge/osx-64
                          https://conda.anaconda.org/nodefaults/noarch
                          https://conda.anaconda.org/nodefaults/osx-64
       base environment : /Users/fperez/local/conda
               platform : osx-64

Logs

No response

environment.yml

No response

~/.condarc

No response

@fperez
Copy link
Author

fperez commented Dec 4, 2024

Excellent, thanks @JohanMabille and @jjerphan for the quick fix!

@jjerphan
Copy link
Member

jjerphan commented Dec 4, 2024

You are welcome, @fperez. 🙂

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.

2 participants