如何在conda环境中将pip作为低优先级的包安装备选渠道？

Great question! I’ve run into this exact scenario before—wanting to prioritize conda’s channels first but use pip as a last resort when a package isn’t available in any conda repository. Let’s break down why your initial approach failed, then walk through practical solutions.

Why Your First Try Didn’t Work #

Conda’s dependency resolver processes all conda-managed package entries before it even looks at the pip section in your environment.yml. When it can’t find some-package>=1.2.3 in defaults or conda-forge, it immediately throws a ResolvePackageNotFound error and stops execution. It never gets to the part where it would install via pip.

Solution 1: Manual Two-Step Installation (Controlled & Simple) #

This approach gives you full control over the fallback logic, and works with any conda version:

1. First, create a base environment with pip included
   Use this stripped-down environment.yml to set up your environment without the problematic package:

   name: my_env
   channels:
     - defaults
     - conda-forge
   dependencies:
     - pip
   

   Create the environment with:

   conda env create -f environment.yml
   

2. Activate the environment and use shell logic to fallback to pip
   Once activated, run this command to first try conda installation, then pip only if conda fails:

   conda activate my_env
   conda install some-package>=1.2.3 || pip install some-package>=1.2.3
   

   The || operator is shell syntax that means "only run the second command if the first one fails".

Solution 2: Use Conda’s pip_interop_enabled (Automated) #

Conda 4.6+ includes a feature called pip_interop_enabled that lets conda automatically fall back to pip when a package isn’t found in conda channels. This is more automated if you need to repeat this setup.

Option A: Enable temporarily during environment creation #

1. Use the same base environment.yml from Solution 1.
2. Create the environment with the interop flag enabled:

   conda env create -f environment.yml --pip-interop-enabled
   

3. Now, when you install packages, conda will handle the fallback automatically:

   conda activate my_env
   conda install some-package>=1.2.3
   

   If conda can’t find the package in its channels, it will call pip to install it for you.

Option B: Enable globally or per-environment #

If you want this fallback behavior to be the default:

• Global setting (applies to all environments):

  conda config --set pip_interop_enabled true
  

• Per-environment setting (only active for my_env):

  conda activate my_env
  conda config --env --set pip_interop_enabled true
  

Important Notes #

• Mixing conda and pip packages can lead to dependency conflicts, since their resolvers don’t communicate fully. Always prefer conda packages when available, and only use pip as a last resort.
• The pip_interop_enabled feature might behave unpredictably with complex dependency chains. Test your environment thoroughly after installation.

内容的提问来源于stack exchange，提问作者Swier