Package Details: python-conda 25.1.1-1

Git Clone URL: https://aur.archlinux.org/python-conda.git (read-only, click to copy)
Package Base: python-conda
Description: OS-agnostic, system-level binary package manager and ecosystem https://conda.io
Upstream URL: https://github.com/conda/conda
Licenses: BSD-3-Clause
Provides: python-conda, python-conda-env
Submitter: cyrevolt
Maintainer: flying-sheep (brianrobt)
Last Packager: brianrobt
Votes: 34
Popularity: 0.113914
First Submitted: 2016-04-08 07:41 (UTC)
Last Updated: 2025-02-04 04:29 (UTC)

Pinned Comments

flying-sheep commented on 2025-01-06 13:01 (UTC)

You forgot to rebuild all your AUR python packages after that update. That's a necessary step and has nothing to do with our conda package.

See e.g. https://www.reddit.com/r/archlinux/comments/1hk2wii/comment/m3g11xz/

Please ask in the Arch BBS or on e.g. Reddit if you have further questions!

Latest Comments

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 Next › Last »

mdeff commented on 2018-05-02 15:35 (UTC) (edited on 2018-05-02 15:40 (UTC) by mdeff)

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:

#!/home/user/miniconda3/bin/python

# -*- 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])
    sys.exit(main())

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 (UTC)

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 (UTC) (edited on 2018-04-04 08:33 (UTC) by cyrevolt)

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 https://github.com/fish-shell/fish-shell/issues/2704 - 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 (UTC) (edited on 2018-03-28 17:41 (UTC) by mdeff)

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 (https://github.com/conda/conda/pull/7101).

cyrevolt commented on 2018-02-21 21:18 (UTC)

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: https://github.com/conda/conda/blob/caedbbfe37860f3b61466408cc9ae199b3ffe910/CHANGELOG.md#4315-2017-03-20

Thanks everyone for helping and enjoy conda! :)

cyrevolt commented on 2018-02-19 00:12 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

Please discuss this at https://aur.archlinux.org/packages/python-ruamel.yaml-hg/ @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.

ardeaf commented on 2017-04-26 22:34 (UTC) (edited on 2017-04-26 22:35 (UTC) by ardeaf)

Can't build python-ruamel.yaml-hg: :: Proceed with installation? [Y/n] y :: Retrieving package(s)... :: python-conda build files are up-to-date -- skipping :: python-ruamel.yaml-hg build files are up-to-date -- skipping [sudo] password for ardeaf: :: Checking python-ruamel.yaml-hg integrity... ==> Making package: python-ruamel.yaml-hg 0.12.14.r1.486262651aa3-1 (Wed Apr 26 12:33:27 HST 2017) ==> Retrieving sources... -> Updating yaml hg repo... pulling from https://bitbucket.org/ruamel/yaml searching for changes no changes found ==> Validating source files with md5sums... yaml ... Skipped :: Checking python-conda integrity... ==> Making package: python-conda 4.3.6-1 (Wed Apr 26 12:33:31 HST 2017) ==> Retrieving sources... -> Found 4.3.6.tar.gz ==> Validating source files with sha512sums... 4.3.6.tar.gz ... Passed :: Building python-ruamel.yaml-hg package(s)... ==> Making package: python-ruamel.yaml-hg 0.14.10.r1.79122dcec309-1 (Wed Apr 26 12:33:32 HST 2017) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> WARNING: Using existing $srcdir/ tree ==> Starting pkgver()... ==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Starting package()... /usr/lib/python3.6/site-packages/pip/commands/install.py:194: UserWarning: Disabling all use of wheels due to the use of --build-options / --global-options / --install-options. cmdoptions.check_install_build_global(options) Directory '.' is not installable. File 'setup.py' not found. ==> ERROR: A failure occurred in package(). Aborting... :: Building python-conda package(s)... ==> Making package: python-conda 4.3.6-1 (Wed Apr 26 12:33:34 HST 2017) ==> Checking runtime dependencies... ==> Installing missing dependencies... error: target not found: python-ruamel.yaml-hg ==> ERROR: 'pacman' failed to install missing dependencies. :: failed to build python-ruamel.yaml-hg package(s) :: failed to build python-conda package(s)

« First ‹ Previous 1 .. 5 6 7 8 9 10 11 Next › Last »