Hey there, let's break down what's going on here first—your terminal is defaulting to Miniconda's Python (that's exactly what the which python output confirms), but packages installed via Pacman live in Arch's system Python's site-packages directory. Since Conda environments are fully isolated from the system Python, they can't see those Pacman-installed files at all. Your earlier pip workaround worked because you were using Conda's own pip, which installs packages directly into the Conda environment's package folder. This time around, it's failing probably due to version mismatches, the package not being available on PyPI/Conda repos, or a wonky Conda environment config.

Here are your best solutions, ordered by how safe and reliable they are:

1. Switch to the system Python for your script #

If your code doesn't rely on any Conda-specific dependencies, just use Arch's native Python directly:

• Temporary fix: Call the system Python's absolute path when running your script. First, find where it lives with:

  which python3
  

  (It'll almost certainly be /usr/bin/python3 on Arch.) Then run your code like:

  /usr/bin/python3 your_script.py
  

• Permanent fix (only if you don't use Conda often): Adjust your PATH so the system binaries come first. Edit your shell config file (~/.bashrc for Bash, ~/.zshrc for Zsh) and add:

  export PATH="/usr/bin:$PATH"
  

  Save it, then run source ~/.bashrc (or your corresponding config file) to apply the change.

2. Install the package in your Conda environment #

Since pip worked before, let's make sure you're using the right pip this time:

• First, activate your target Conda environment (skip this step if you're using the base env):

  conda activate your_env_name
  

• Try installing via Conda first (it handles dependency resolution better than pip):

  conda install package_name
  

• If Conda doesn't host the package, use Conda's pip (don't just run pip—that might accidentally call the system pip!):

  python -m pip install package_name
  

  Using python -m pip guarantees you're using the pip tied directly to your active Conda environment.

3. Manually link system packages to Conda (use as last resort) #

If the package only exists in Arch's repos and nowhere else, you can force Conda to see it—but this can cause messy dependency conflicts, so proceed carefully:

• Find the system Python's site-packages directory:

  /usr/bin/python3 -c "import site; print(site.getsitepackages())"
  

  You'll get a path like ['/usr/lib/python3.11/site-packages'] (adjust the version number to match your system Python).
• Create a .pth file in your Conda environment's site-packages folder that points to this path:

  echo "/usr/lib/python3.11/site-packages" >> /home/username/miniconda3/lib/python3.6/site-packages/system-packages.pth
  

  Make sure the Python versions are as close as possible—mismatched versions will almost certainly break things.

Quick Checks to Rule Out Other Issues #

• Confirm you're in the right Conda environment: Run conda info --envs—the active environment will have a * next to it. If it's not the one you want, activate the correct one.
• Verify the Pacman package actually installed correctly: Test importing it in the system Python with:

  /usr/bin/python3 -c "import package_name"
  

  If this throws an error, reinstall the package with sudo pacman -S python-package_name.

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