Скачать или смотреть Resolving Python Version Issues in Conda Environments: The python --version Dilemma

Facing an issue with Conda where the Python version doesn't change after activating a new environment? Discover how to fix the problem caused by aliasing Python in your system!
---
This video is based on the question https://stackoverflow.com/q/66095550/ asked by the user '刘江斌' ( https://stackoverflow.com/u/14609458/ ) and on the answer https://stackoverflow.com/a/66128880/ provided by the user 'merv' ( https://stackoverflow.com/u/570918/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Why I conda activate env with python3.7, but python version still is python3.5?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the Conda Activation Issue: Why Is Python Still Showing an Old Version?

If you've ever created a new Conda environment and found that the Python version doesn't change as expected, you're not alone. This issue can be particularly perplexing for new users of Miniconda or Anaconda on systems like Ubuntu. In this post, we'll unravel the mystery behind why running python --version might still point to an old version even after attempting to activate a new environment.

The Problem Explained

You may have created an environment using the following command:

[[See Video to Reveal this Text or Code Snippet]]

After activating this environment with:

[[See Video to Reveal this Text or Code Snippet]]

you expect the command python --version to reflect Python 3.7. Instead, you notice that it still displays an older version, such as Python 3.5.2. This situation can become even more frustrating when you create additional environments, such as for Python 2.7, and the same version issue persists.

So, what could be at the root of this problem?

Digging Deeper: Debugging the Conda Environment

Upon investigation, you find out that typing type python reveals that python is aliased to /usr/bin/python3.5.2. This means that your terminal is not using the Python version from the activated Conda environment; instead, it's defaulting to the system Python interpreter.

To further analyze the situation, you might check your .bashrc file and discover a line that looks like this:

[[See Video to Reveal this Text or Code Snippet]]

This line effectively tells your terminal to always use Python 3.5.2 when you type python, regardless of which Conda environment you're in. This aliasing behavior overrides any version specified by your Conda environment, leading to confusion.

The Solution: Removing the Alias

To resolve this issue, the simplest and most effective solution is to remove the alias altogether. It’s not compatible with how Conda environments are designed to function. Here’s how you can do it:

Open Your .bashrc File:

You can open this file using a text editor:

[[See Video to Reveal this Text or Code Snippet]]

Locate and Remove the Alias:

Find the line containing the alias for Python:

[[See Video to Reveal this Text or Code Snippet]]

Delete or comment out this line to prevent it from being used when you start a new terminal session.

Save and Exit:

After making the changes, save the file and exit the text editor (for Nano, press CTRL + X, then Y, then Enter).

Refresh Your Terminal:

Once you’ve made the changes, refresh your terminal session:

[[See Video to Reveal this Text or Code Snippet]]

Verify the Changes:

Now, try activating your Conda environment again:

[[See Video to Reveal this Text or Code Snippet]]

Finally, check if the Python version has updated by running:

[[See Video to Reveal this Text or Code Snippet]]

You should now see that it reflects the correct version (Python 3.7 for the py37 environment).

Conclusion

The issue of a stubborn Python version showing an older release after activating a Conda environment is commonly due to an alias set in your terminal configuration. By removing this alias, you can allow Conda's version management to operate correctly, ensuring that your environments behave as expected.

For any other issues or further questions about managing Python environments, feel free to ask in the comments below. Happy coding!