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 »

tr3s commented on 2018-05-10 22:25

I'm having this issue when creating conda environment:

Solving environment: failed

NotWritableError: The current user does not have write permissions to a required path. path: /usr/pkgs/urls.txt uid: 1000 gid: 1000

If you feel that permissions on this path are set incorrectly, you can manually change them by executing

$ sudo chown 1000:1000 /usr/pkgs/urls.txt

In general, it's not advisable to use 'sudo conda'.

Sorry for the format :)

mdeff commented on 2018-05-02 15:35

Great! Thanks for your work cyrevolt :)

For completeness, here's the content of the conda script as generated by the miniconda installer on one of my machines:


# -*- coding: utf-8 -*-
import re
import sys

from conda.cli import main

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])

conda-env is the same, except that from conda.cli import main becomes from conda_env.cli.main import main (as you are doing in the PKGBUILD).

BTW completion is working perfectly for me on the fish shell. I don't think there's completion for any other shell though.

cyrevolt commented on 2018-05-02 00:13

I have figured out how to get conda-env to work and it is now included. Enjoy! :)

cyrevolt commented on 2018-04-04 08:23

Thank you for your suggestions mdeff!

1. I've looked into conda-env, and it is part of the main conda repo, and it is even being installed. I cannot find a conda-env executable file though. The README says even that it should be installed into the "base environment" by running: conda install -c conda conda-env I am not sure how this can be simply added to the package yet.

2. I a m not a csh user; I know setenv from fish, which appears to be just a compatibility thing and should actually be set -x, according to - it is the counterpart to bash's export, if I understand correctly. I am using it in the -git version of this package. I need to read more about this.

3. Well if we don't use setenv / set -x for zsh and fish, it makes sense to remove the export for bash also. It should be the same for all shells. I'll investigate.

4. Yup, I'm adding it. I am not sure yet though what the completion actually provides. I tried it out, but conda bu for example does not complete in neither shell. I opened a new terminal and even sourced the respective file again.

5. Awesome! I should also reach out to upstream to clarify packaging issues. The seemed to prefer the curl pipe sudo bash pattern to avoid/circumvent distro packaging so far. I hope they will be cooperative. :)

mdeff commented on 2018-03-28 17:40

I've spotted some issues with that package:

  1. /usr/bin/conda-env is not installed. I guess this file (along with /usr/bin/conda) is generated by the installer. Without conda-env users cannot access the conda env commands, e.g. conda env export.
  2. Does the csh shell needs setenv instead of set? (installer uses setenv)
  3. The bash shell does not need export (the variable can stay private, as done by the installer)
  4. Similarly to _CONDA_EXE, _CONDA_ROOT should be set to /. For fish, set _CONDA_ROOT / (it is used for auto-completion).
  5. I've submitted a PR to auto-complete conda env in fish (

cyrevolt commented on 2018-02-21 21:18

The issues are now fixed and it works again. :) I tested with bash, fish, and zsh.

You may need to set pkgs_dirs in your condarc. To do so, you can use the CLI:

Thanks everyone for helping and enjoy conda! :)

cyrevolt commented on 2018-02-19 00:12

I am sorry for fish users. Version 4.4 changed the shell integration again.

After conda activate, you cannot use conda anymore. It will raise the error ImportError: No module named 'conda'. If anyone has a solution, I'd be happy to know - and everyone else surely. :) To get this to work at all, I had to inject the path to the /usr/bin/conda script into the fish script that has to be sourced. And that one actually reads "# WARNING: Not a real conda entry point. Do not use other than for tests.".

cyrevolt commented on 2017-11-24 11:16

Thanks everyone here for letting me know about updates!

With the most recent bump, I also updated the other conda tools, i.e., conda-verify and conda-build. They both made major changes from v2 to v3. :)

cyrevolt commented on 2017-05-07 20:52

I have now switched to using the stable python-ruamel-yaml from the community repo and updated to 4.3.17. I also read that 4.4 should be released somewhat soon.

I hope everything is fine now. :)

cyrevolt commented on 2017-04-26 22:45

Please discuss this at @ardeaf

I'm not much familiar with Mercurial, but I would suggest to try checking out an older revision when building, i.e. adjusting the PKGBUILD for it.