Скачать или смотреть Understanding the Differences Between Anaconda and Native Python pip Paths on macOS

Learn how to manage Python environments on macOS, including troubleshooting `pip` installation issues between Anaconda and native Python.
---
This video is based on the question https://stackoverflow.com/q/62598350/ asked by the user 'Hubert Schölnast' ( https://stackoverflow.com/u/1302716/ ) and on the answer https://stackoverflow.com/a/62599245/ provided by the user 'Emerson Harkin' ( https://stackoverflow.com/u/13568555/ ) 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: pip path: anaconda vs. native python (on macOS)

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.
---
Navigating pip Paths: Anaconda vs. Native Python on macOS

When it comes to Python development on macOS, a common dilemma arises: how to manage packages using pip when multiple Python installations exist? For users who have installed both Native Python and Anaconda, this challenge can lead to confusion and frustrating errors. Today, we’ll explore the best strategies for managing these installations effectively and ensuring your Python scripts can access the necessary packages, such as ffmpeg.

The Problem Described

You have Native Python 3.8 installed on your macOS, saving packages in a specific path:

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

Later, you installed Anaconda, which saves packages in a different directory:

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

While trying to install ffmpeg, you successfully ran:

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

However, when you attempted to run your script, it couldn't locate ffmpeg. Upon reinstallation, pip indicated the package was already satisfied in the Anaconda path, hence the discrepancy.

You’re left with three questions:

Is it safe to manually copy directories between Anaconda and native installs?

How can you direct pip to install packages in the native Python environment?

Is merging the two site-packages directories beneficial, and if so, how can it be done safely?

Solutions and Recommendations

1. Avoid Manual Modifications to site-packages

The advice here is clear: do not manually copy directories between environments. Here are a few reasons why you should avoid this approach:

Dependency Issues: Manually modifying site-packages can introduce conflicts and complicate your dependency management.

Virtual Environment Management: Tools like Anaconda are specifically designed to handle multiple Python environments. These tools eliminate the need for manual management.

If you require both Python versions for different projects, consider creating separate environments within Anaconda using the command:

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

Activate the environment with:

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

2. Utilizing the Correct pip

When installing packages, it’s crucial to use the correct version of pip that corresponds to your desired Python installation. Here's how:

Confirm the Active Python and pip Version

Run the following commands to check which Python and pip are currently active:

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

If you need to switch to Native Python, deactivate Anaconda:

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

Check Symlinks

In some cases, the pip command may point to different installations through symlinks. You can check this by running:

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

Special Note on pip3

Remember that the pip for your Native Python 3.8 may be labeled as pip3, so make sure to use the appropriate command during package installations.

3. Verifying Package Install Locations

To ensure that your packages are installed in the correct environment, you can check the installation path of a package. Use:

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

This command will provide the installation location for that package, allowing you to verify where it is being installed.

Conclusion

Managing multiple Python installations on macOS can lead to challenges, particularly regarding package management with pip. By avoiding manual copying of site-packages, utilizing the correct versions of pip, and verifying installation paths, you can streamline your workflow and avoid common pitfalls. Remember, the key to effective Python development is using the right tools and environments that prevent conflicts and mai