Under "Steps for applicants to conda-forge:",
line 6
I found this:
"Codetribute is a site that guides contributors to their first contribution. It helps new contributors find a project they want to work with, learn about that project, and then find a task that is suitable to their skills and interests and not already assigned to someone else.
"
@ForgottenProgramme I saw it at https://conda-forge.org/blog/posts/2021-02-02-Outreachy/;
Under "Steps for applicants to conda-forge:",
line 6
HI, indeed that line was not supposed to be there, the goan in the paragraph was to remind everyone to submit their contributions to Outreachy and have a good experience (yeah codetribute is a mozilla thing). Thanks for the review. I didn't notice that term there before.
1 reply
dvc). In the run requirements for the secondary packages, there is the macro - {{ pin_subpackage("dvc", exact=True) }}. I added a run requirement (importlib-metadata) to the main package (dvc) but this doesn't seem to be getting picked up by any of the secondary packages. Perhaps pin_subpackage is pinning the anaconda.org version instead of the local version? Any idea how to fix this?
On travis I'm getting: docker:
failed to register layer: Error processing tar file(exit status 1): write /opt/conda/pkgs/gettext-0.19.8.1-hf23c357_1005/share/doc/gettext/examples/hello-c++-wxwidgets/po/bg.po: no space left on device.
204See 'docker run --help'.
205The command "if [[ ${PLATFORM} =~ .*linux.* ]]; then ./.scripts/run_docker_build.sh; fi" exited with 125.it there something to do?
Hi all, I have a very general question about mamba vs conda.
Six months ago I was on the verge of giving up on the Conda ecosystem because conda was so unbearably slow. I wanted to manage my development environment using conda where I had lots of tools installed. If I wanted to install anything "the right way" using conda I would have to wait literally ½-hour for the solver to complete. On the other hand, pip works virtually instantaneously.
Thankfully I discovered mamba just in time before I gave up. The solver completes in seconds, regardless of my environment's size. In the following months I have become convinced that conda-forge has a bright future thanks to mamba. I'm so convinced that over the past month I've been dedicating a lot of my time to creating and maintaining conda-forge feedstocks.
Along the way I have encountered several people who were similarly frustrated because they didn't know about mamba, for instance https://github.com/pyscaffold/pyscaffoldext-dsproject/issues/7#issuecomment-791723904 and iterative/dvc#5625 . I really get the impression that I'm usually the only person in a conversation who knows of mamba.
I believe the reason why nobody knows about mamba is fairly evidently the lack of promotion, in particular by conda-forge. See here: iterative/dvc.org#2370
From my perspective, I observe conda-forge massively bleeding users due to conda being borderline unusable. Although "experimental", in all the time I've been using mamba I find it far more stable and reliable than conda. I understand the reluctance to confuse users with a new command, but I'm convinced that the benefits are well worth more than the passing mention in the conda-forge FAQ.
Would it be possible for conda-forge to endorse mamba more strongly so that it's more discoverable, and so that projects like iterative/dvc.org#2370 would be comfortable recommending it when appropriate?
1 reply
mamba but I could expect that there are still some things to tackle before doing this conda-forge globally. But as we already ship mambaforge as the kind of preferred installer, we are already quite near. @bmares_gitlab Could you make a PR to the docs on where you would like to have a more visible "support" of mamba? Then I would expect if there is opposition that it would pop up in that PR and we can see together from there what needs to be done.
conda, we'd make the box fatter, and have conda or mamba, conda-build or boa, etc.
staged-recipes as a proxy for "new start work" seems stable, after an initial COVID hit
Hey all!
I'm Mahe. I was reading the above discussion about mamba.
I'm an Outreachy applicant and I have noticed a lack of documentation around mamba in the conda-forge docs.
We have been trying to hold discussions around this to decide whether mamba merits a dedicated page in the conda-forge docs or atleast a dedicated section. And what all information should go in there.
This discussion above could be helpful for us when we write up the docs. Hopefully we'll reach some mutual decision around this soon. :)
environment.yml like python=*=*_pypy? conda-incubator/setup-miniconda#170
2 replies