Package Details: python-conda 4.9.2-1

Git Clone URL: (read-only, click to copy)
Package Base: python-conda
Description: OS-agnostic, system-level binary package manager and ecosystem
Upstream URL:
Licenses: BSD
Provides: python-conda, python-conda-env
Submitter: cyrevolt
Maintainer: cyrevolt (specter119)
Last Packager: cyrevolt
Votes: 23
Popularity: 0.37
First Submitted: 2016-04-08 07:41
Last Updated: 2020-12-14 22:52

Dependencies (7)

Sources (1)

Pinned Comments

cyrevolt commented on 2020-12-14 23:01

Traceback (most recent call last):
  File "/usr/bin/conda-build", line 33, in <module>
    sys.exit(load_entry_point('conda-build==3.20.5', 'console_scripts', 'conda-build')())
  File "/usr/bin/conda-build", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib/python3.9/importlib/", line 77, in load
    module = import_module('module'))
  File "/usr/lib/python3.9/importlib/", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 790, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/usr/lib/python3.9/site-packages/conda_build/cli/", line 12, in <module>
    from glob2 import glob
ModuleNotFoundError: No module named 'glob2'

If you see something like this, the "error" is that AUR packages are not rebuilt when the system Python version is upgraded, which just happened again with 3.9. You need to manually upgrade each and every Python package from AUR, unfortunately. That is quite a caveat, because not everyone notices that something specific like Python is upgraded when they run pacman -Syu and see a list of 200 or more packages. This also happens with Node.js and what not.


So I have just bumped the package here as well as python-conda-build, which triggers updates with e.g. yay -Su. However, some dependencies may not have a new version now. What we could do for this case is to increase pkgrel for those other packages. It feels hacky, but at least it works.


I am sorry for the inconvenience. Now the remaining problem is: Because of the bunch of dependencies and dependencies of dependencies, it is easy to miss one of them. =) Secondly, I do not own all the dependencies, so some will need manual maintenance either way, unfortunately. For example, you will need to reinstall python-glob2-git. Please let us know here if anyone of you runs into issues and we will try to help.


To rebuild, you need to pass the --rebuild option.

Example: yay -S python-glob2-git --rebuild

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

cyrevolt commented on 2019-06-17 15:01

I guess it's somewhat related to - I'll see if I can find a fix. They are changing how paths and environments are being handled from time to time. That caused me a headache a few times already. :D

bobschi commented on 2019-06-17 09:48

After installing this package I manually have to add

export CONDA_EXE=/usr/bin/conda

to .bashrc, otherwise it won't work. Any ideas on that?

Stendec commented on 2019-06-14 17:56

There's a weird dependency circle with python-conda-package-handling when starting from scratch (neither python-conda or python-conda-package-handling installed). They both depend on each other and neither will build.

This can be circumvented by first installing python-conda-git, then python-conda-package-handling, and THEN python-conda, but this seems a little non-ideal.

cyrevolt commented on 2019-06-13 20:14

Please see the respective package:

TL;DR: fixed

kristerv commented on 2019-06-13 10:50

Install fails

==> Making package: python-conda-package-handling 1.3.4-1 (Thu 13 Jun 2019 01:47:01 PM EEST)
==> Retrieving sources...
  -> Found 1.3.4.tar.gz
==> Validating source files with sha512sums...
    1.3.4.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: python-conda-package-handling

just for info: installs. edit: never mind, they don't include python-conda-package-handling.. also I'm now understanding the problem is with python-conda-package-handling and not python-conda - moving over.

mdeff commented on 2018-06-04 13:34

That's expected. The "base environment" is located under the /usr system directory and is not writable by users. That's because you installed conda system-wide with this package. If you'd instead installed it with e.g. the installer provided by continuum, the base environment would be situated under your home directory and you'd update with conda update conda.

Pixys commented on 2018-06-04 12:35

Thank you. I switched back to the "base environment" just to test and I have the same error. Anyway, I trust you on the update through AUR so thanks again.

mdeff commented on 2018-06-04 11:51

conda is not installed in your environment test01, but in the "base environment". If you installed conda with this package, there's no need for conda update conda though. You should update it with whatever AUR helper you're using.

Pixys commented on 2018-06-02 05:45


I just installed python-conda (fresh installation). When I run 'conda update conda', here is what I get. Thanks for your help!

$ conda update conda

PackageNotInstalledError: Package is not installed in prefix.
prefix: /home/$USER/.conda/envs/test01
package name: conda


See the ouput of 'conda info -a':

$ conda info -a

    active environment : None
            shell level : 0
    user config file : /home/$USER/.condarc
populated config files : /home/$USER/.condarc
      conda version : 4.5.4
conda-build version : 3.10.5
     python version :
   base environment : /usr  (read only)
       channel URLs : <>
      package cache : /home/$USER/.conda/pkgs
   envs directories : /home/$USER/.conda/envs
           platform : linux-64
         user-agent : conda/4.5.4 requests/2.18.4 CPython/3.6.5 Linux/4.16.13-1-ARCH arch/ glibc/2.27
            UID:GID : 1000:1000
         netrc file : None
       offline mode : False

# conda environments:
test01                *  /home/$USER/.conda/envs/test01
base                     /usr

sys.version: 3.6.5 (default, May 11 2018, 04:00:52) 
sys.prefix: /usr
sys.executable: /usr/bin/python3
conda location: /usr/lib/python3.6/site-packages/conda
conda-build: /usr/bin/conda-build
conda-convert: /usr/bin/conda-convert
conda-develop: /usr/bin/conda-develop
conda-env: /usr/bin/conda-env
conda-index: /usr/bin/conda-index
conda-inspect: /usr/bin/conda-inspect
conda-metapackage: /usr/bin/conda-metapackage
conda-render: /usr/bin/conda-render
conda-skeleton: /usr/bin/conda-skeleton
conda-verify: /usr/bin/conda-verify
user site dirs:

CIO_TEST: <not set>
MOZ_PLUGIN_PATH: /usr/lib/mozilla/plugins
PATH: /home/$USER/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
SSL_CERT_FILE: <not set>

WARNING: could not import _license.show_info
# try:
# $ conda install -n root _license

mdeff commented on 2018-05-11 12:14


  - ~/.conda/pkgs
  - ~/.conda/envs

to your ~/.condarc.

It should probably be reported upstream that the default paths should be relative to the user home, not relative to the base directory.