-
Notifications
You must be signed in to change notification settings - Fork 382
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
Python version change #82
Comments
Thanks for submitting this. I presume that if the mamba behavior is to be considered incorrect, it means that some packages should special-cased to never be downgraded or upgraded unless explicitly required? |
Yes, if mamba is to be a drop-in for conda. |
Is it only python, or also other interpreters or packages? |
I've no idea. Sorry. |
It's only python as far as i am aware. This should be easy to fix by pinning python to the currently installed version. |
this is fixed by pinning python if it's in the environment. Release is out now (0.1.1) and going to be available on conda-forge soon! |
Thanks for fixing this. |
I don't have a reproducer where python version was upgraded, but here's an example
conda create -p /home/isuru/miniconda3/envs/py37 python=3.7
conda install opbeat -p /home/isuru/miniconda3/envs/py37 # this errors because opbeat need py<37
mamba install opbeat -p /home/isuru/miniconda3/envs/py37 # Downgrades python to 3.6
The text was updated successfully, but these errors were encountered: