Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 02:23
    kalefranz commented #9255
  • 02:22
    kalefranz commented #9255
  • 02:13
    MetaQiime opened #9256
  • 02:08
    tabbal commented #8972
  • 01:34
    msarahan commented #9255
  • 01:34
    msarahan edited #9255
  • 01:34
    msarahan commented #9254
  • 01:33
    msarahan edited #9254
  • 01:26
    msarahan commented #9254
  • 01:20
    asford commented #9254
  • 01:18
    asford commented #9254
  • 01:18
    cla-bot[bot] commented #9255
  • 01:18
    cla-bot[bot] labeled #9255
  • 01:18
    msarahan commented #9255
  • 01:17
    msarahan commented #9255
  • 01:17
    msarahan commented #9254
  • 01:12
    cla-bot[bot] commented #9254
  • 01:12
    cla-bot[bot] labeled #9254
  • 01:11
    msarahan commented #9254
  • 01:11
    msarahan commented #9255
Ray Donnelly
@mingwandroid
It should have been, yes!
Teake Nutma
@teake
@mingwandroid Oh ok then I feel less silly. So that’s a genuine bug? Feel free to reopen conda/conda#9212 then.
Ray Donnelly
@mingwandroid
You can add -c anaconda. But we should be unmixing these from anaconda.org/anaconda now I feel (and forcing people who want to use free to add -c free because it's full of less well built software that I personally wouldn't run)
But unmixing may not be possible, I need to check with the team
Teake Nutma
@teake
I think the most confusing for me is that the pkgs/free packages on https://anaconda.org/anaconda are labeled main.
Ray Donnelly
@mingwandroid
main here is in a totally different context, but sorry about the exact string match
labels != channels
Teake Nutma
@teake
Yeah that’s probably the root of my confusion.
Ray Donnelly
@mingwandroid
main was my idea for the new channel with the good stuff, didn't think of the label named main at the time tbh.
we did spend a while on this trying to avoid such, oops.
Olaf
@randomgambit
hello I have installed the latest July 2019 anaconda distrib, but when I run conda install a lot of packages require to downgrade to custom python 3.7 (instead of the July 2019 version) . Is that expected? thanks!!
that is, going from anaconda 2019.07.py37_0 to custom-py37.1
is this problematic?
Sophia Castellarin
@soapy1
yep, this is expected. This blog post talks a bit about what you are seeing https://www.anaconda.com/whats-in-a-name-clarifying-the-anaconda-metapackage/
Olaf
@randomgambit
👍
luzpaz
@luzpaz
Quick question: I'm running Manjaro Linux and I'm interested in testing something that requires conda for dependency management, how do I install and run conda on my box without it borking pacman ?
luzpaz
@luzpaz
soft bump
Uwe L. Korn
@xhochy
@luzpaz Just install miniconda from https://docs.conda.io/en/latest/miniconda.html The created environments are totally distinct from your system package managers.
luzpaz
@luzpaz
@xhochy Just do it is still not creating more confidence. I understand that I will be asked to add miniconda to the system path. so that the python version of miniconda will be utilized over my system python, correct? How will this not mess things up on my system ?
Uwe L. Korn
@xhochy
@luzpaz Only the people that have conda installed and use this should make the Python first in their PATH. It is preferable between to install anaconda/miniconda on a per-user basis and not system-wide.
Benjamin Bertrand
@beenje
@luzpaz With recent version of conda, if you use conda config --set auto_activate_base false then the default conda base environment won't be activated by default and your PATH will stay unchanged. conda is just a function.
luzpaz
@luzpaz
@beenje do i need to deactivate it when I'm done using it ?
I'm trying to QA test something...and need a setup that is contained and won't pollute the rest of the system. I need it to be idiot proof so if I forget that I enabled it and then run a system update that the conda environment won't be used and potentially b0rk the system
Benjamin Bertrand
@beenje
If you activate the environment, you have to deactivate it after (but it only impacts your current running shell, it's not global). So you can just close your shell as well. After you might not even have to activate the environment to use it. You can for example run a command installed in a conda environment by giving its full path. I do that for tools like flake8 or black. I use an alias pointing to the full path.
luzpaz
@luzpaz
can you show me an example of said alias ?
Benjamin Bertrand
@beenje
alias black='/Users/benjaminbertrand/miniconda3/envs/black/bin/black'
Ray Donnelly
@mingwandroid
Ideally you'd be able to use: alias black='conda run -n black black' .. but conda run is probably not quite ready for that.
It does work, to some extent though, even on Windows/MSYS2 shell.
The advantage is that any activation and PATH manipulation that needs to take place will take place.
Ray Donnelly
@mingwandroid
for this to run correctly type conda must indicate that it is a shell function and not anything else.
luzpaz
@luzpaz
Ok, thanks for the help.
p
@pssweig_gitlab
hello. I downloaded anaconda but I only get the prompt box. I can't figure out how to actualy open the program to the part where you code. Also, I need spyder and I'm not sure how that differs from anything. I have windows. Can anyone help me figure this out? Thanks!
Pav A
@rs2
All, can I please check the expected date for the next conda release? https://github.com/conda/conda/compare/4.7.11...master
Mike Sarahan
@msarahan
probably later today.
Pav A
@rs2
:+1:
Mike Sarahan
@msarahan
Conda 4.7.12 is released and available on the conda-canary channel. It will be on defaults on Monday, assuming no major issues are reported in the meantime.
Pav A
@rs2
:+1:
When do you expect to do the next release of conda-build please?
DSM
@dsm054
Could I bribe someone into looking at conda/conda#9220 ? I'm willing to work up a PR, but I wouldn't mind some independent confirmation that I'm on the right track. ;-)
Christian Roth
@croth1

Argh, I did not pay attention and conda updated python 2->3 in my base environment after doing conda update -n base --all
Now I am in state where conda is still in lib/python2.7/conda/..., but the interpreter is python3.7, therefore when calling conda I now get this:

Traceback (most recent call last):
  File "/usr/users/croth1/miniconda/bin/conda", line 7, in <module>
    from conda.cli import main
ModuleNotFoundError: No module named 'conda'

Any recommendations what's the best way to go from here?

Theo McCaie
@tam203

Hi I have a question that I hope someone might be able to help with:

The context is that we have a Zero2Jupyter set up on Kubernettes and our single user docker images are big (6+GB) a large amount of this is a very heavy conda environment. We are really keen to shrink our image sizes.

One idea to do this is to create a docker image with a vanilla miniconda install and create a cloud filesystem with our heavy conda environment (read-only shared across our users) and mount that in at ROOT_DIR/env/my-env

What I'm not clear on is:

  1. could this work?
  2. How would we make the env (would it be enough to make it on one machine and then copy everything in ROOT_DIR/env/my-env our cloud storage?
  3. Is there anything that's shared across environments /pkgs feels like it is from reading the docs
  4. If /pkgs is shared if I did a deep copy (i.e. following softlinks) when creating my shared env might that work?
  5. Any precedents/examples of this out there?

A lot of questions, your help really appreciate.

Uwe L. Korn
@xhochy
@tam203 you might also want to take a look at https://conda.github.io/conda-pack/ for your case
Theo McCaie
@tam203
@xhochy ooooh that looks promising. Thanks.
Pav A
@rs2
@msarahan How do you feel about cutting another release of conda-build?
Mike Sarahan
@msarahan
@mingwandroid is working on some fixes to the library inspection code. We'll think about a release when he's ready.
Ray Donnelly
@mingwandroid
Yeah, sorry about this, definitely needing a release.
Benjamin Bertrand
@beenje
According to the documentation either conda remove --name myenv --all or conda env remove --name myenv can be used to remove an environment. I noticed they don't exactly do the same. conda remove --all first removes all packages before to remove the env. conda env remove doesn't. Is that historical? Is one way preferred?
Christian Roth
@croth1
In order to fix a broken conda installation I had to use pip to bootstrap dependencies of conda. These dependencies are now listed as pypi packages in the output of conda list. Is there a way to ask conda to replace them with conda packages again?
Mike Sarahan
@msarahan
you probably need to enable pip interop: conda config --set pip_interop_enabled true
then you should be able to just conda install your thing. If it says that it is already satisfied, you can try the --force-reinstall flag