![]() ![]() Other versions are available to load as modules. However, Mamba seems to give more sensible feedback (and much faster): $ mamba create -n snakes python=3.5.3 python=3.7.1 PackagesNotFoundError: The following packages are not available from current channels: Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.Ĭollecting package metadata (repodata.json): done Simply trying to install both with Conda doesn't give a clear error, in my opinion: $ conda create -n snakes python=3.5.3 python=3.7.1Ĭollecting package metadata (current_repodata.json): done Then activate to use the environment of choice: conda activate python3_7_1 Instead, create a separate environment for each Python version (or, better, for each project): # v3.5.3 environment (name is arbitrary)Ĭonda create -n python3_5_3 python=3.5.3 # also include additional packages here ![]() ![]() As commented, it is a central purpose of environments to isolate different Python installations from each other. One cannot install different Python versions in the same environment. Luckily, managing multiple versions of Python doesn’t have to be confusing if you use pyenv. Please take time to read the Conda documentation, which covers using different Python versions. Are you ever curious about the latest and greatest versions of Python Maybe you’d like to try out these new features, but you don’t want to worry about messing up your development environment. ![]()
0 Comments
Leave a Reply. |