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

conda create with python2.7 base still creates python3.6 environment by default #90

Closed
mattf-apache opened this issue Aug 31, 2019 · 5 comments
Labels
locked [bot] locked due to inactivity type::support neither a bug nor feature, is really just a user having questions or difficulty somewhere

Comments

@mattf-apache
Copy link

If one downloads Miniconda2-latest-MacOSX-x86_64.sh and runs it, you get as expected a python2.7 base environment. Go ahead and activate it, then invoke conda create with a few packages, but without specifying a version of python. It builds a python3.6 environment.

I could not find documentation one way or the other, but I did expect it to give me another python2.7 environment, especially since I had activated the base environment before invoking conda create.

@marcelotrevisani
Copy link
Member

marcelotrevisani commented Aug 31, 2019

Basically conda will try to get the latest package of all of those which you are trying to install.
However, if you want a conda environment with a specific python you can do

conda create --name env-test python=2.7 

@marcelotrevisani marcelotrevisani added the type::support neither a bug nor feature, is really just a user having questions or difficulty somewhere label Aug 31, 2019
@marcelotrevisani
Copy link
Member

Did I clarify your question? May I close this or do you want to discuss it a bit further?

@jcrist
Copy link
Collaborator

jcrist commented Sep 3, 2019

This has nothing to do with conda-pack, this has to do with usage of conda. If you want to create a python environment with a specific version of Python, you need to specify that manually as @marcelotrevisani said above. Closing.

@jcrist jcrist closed this as completed Sep 3, 2019
@mattf-apache
Copy link
Author

mattf-apache commented Sep 3, 2019

So be it. This was to suggest that a more intuitive behavior was to give the same version as the base, by default. But it's also reasonable for conda to always use the latest, regardless of base.
Thanks for consideration.

@github-actions
Copy link

Hi there, thank you for your contribution!

This issue has been automatically locked because it has not had recent activity after being closed.

Please open a new issue if needed.

Thanks!

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Mar 17, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 17, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity type::support neither a bug nor feature, is really just a user having questions or difficulty somewhere
Projects
None yet
Development

No branches or pull requests

3 participants