-
Notifications
You must be signed in to change notification settings - Fork 70
Default to py3 for new conda projects #86
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
Comments
I think we should start forcing this. We are close to the end of the Python2 support and people using conda environment usually specifies the version of Python they want to install in the |
Install Python 3.10.0b3 and upgrade to Miniconda3-py38-4.9.2. > NOTE that Miniconda3-py39_4.10.1 is not available for Linux x86_64 so I had to > pick the previous one Upgrading Miniconda2 to Miniconda3 changes the default behavior when the user doesn't specify the python version (`build.python.version`). The environment will be created with Python3 by default now instead of Python2. See #86 I don't think this will affect too many users since this PR is going to be merged into `release/7.x` branch (`testing` image) that only a few users are currently using.
New Docker images (#166) will require the user to explicity define the conda version they want to install. If the select We don't need to take any other action here. |
Considering that we are defaulting to
python3
for new projects (readthedocs/readthedocs.org#3581) we need to do the same for projects that usesconda
instead ofpip
.This can be achieved by using
Miniconda3
instead ofMiniconda2
. The problem of changing this is that if the user was not specifying the Python version,python2
was installed and nowpython3
will be installed, which may break the build.We need to research a little more about this and make some tests.
Discussion: #84 (comment)
The text was updated successfully, but these errors were encountered: