I'm trying to figure out if I can build something on defaults without using conda-forge
since it's a bit more complicated using them...
and no MKL etc...
1 reply
(and I don't know)
Setuptools was trying to resolve some packages in pip (and not specifying which ones...) without it.
In other news though, I'm getting a problem with the linux docker build now...
I've got my meta.yaml like this:
run:
- {{ openmp }}
- python
- numpy
- cffiand my conda_build_config.yaml looks like this:
openmp:
- intel-openmp # [linux]
- llvm-openmp # [osx]but the meta.yaml after substitution is just blank.
run:
-
- python
- numpy
- cffiIt works fine on OSX....
I have an anaconda environment that's pretty damn large (~1.5GB) the size is unavoidable as they're all really large math and CAD libraries. I need to distribute the environment along with my application, which is the tricky part since it's actually a .Net app that interfaces through PythonNet.
What would be the best way to get the environment to the end user? Should I just literally copy paste the environment files into the compiled application so that users download it with the app? Is there a tool I can use to build the environment during the app install? Not sure what the best way to go is.
I use environment.yml files to create my conda environments. From the command-line I can use "conda env create -f environment.yml" to create an env. However I would like to use the python API to do this, but "env" is not included as a command in the python api.
- Is there anyway to create an env from a yml file using the python api?
- Why isn't there an option in "conda create" to use the yml file? "--file" doesn't work with a yml file. Would this be straight forward to add?
- How did the "conda env" command, which is only partially documented and supported, come about? Why is it a seperate command, rather than a part of the "conda create" command options?
it's the mechanism that's used to build miniconda and miniforge though
Are you referring to this issue mopemope/meinheld#121 ? In any case it is difficult to debug remotely, even more so on gitter. Please open an issue on the issue tracker of the project that is giving you "library file errors" and ping me @mattip there
3 replies
Hoping we get some motion on this soon; otherwise the scientific software we package on conda-forge for Win+OSX+Linux will eventually need to give up on Tensorflow, on OSX, or on Conda as its main distribution mechanism. None of those are great options.
conda 4.10.0 has been published to the conda-canary channel; changelog is here: https://github.com/conda/conda/blob/4.10.0/CHANGELOG.md. Barring any major issues, we will be releasing it to the defaults channel on Tuesday (6 Mar.)
Hi! When I install a package one of the feedbacks printed out says "Updating specs with <pkg_name>". I understand that the specs for an env are all packages that the user specifically asked for versus all other packages in the env that were drawn in from the depenency tree. Is there a CLI to look at the specs only vs listing all packages? I would expect such option in
conda list but cannot see it in the docs there.
Has anyone run into issues with setuptools/cmake based projects where cmake ends up linking against the system, rather than conda glibc? I just updated my workstation, and now my project fails to compile/run since the libstdc++ bundled with conda doesn't offer GLIBCXX_3.4.29
hey guys, i'm wondering how long it will take before the index gets updated....
I see my package here with version 0.7.53 https://anaconda.org/conda-forge/cliche
but here it still shows 0.7.52 https://conda.anaconda.org/conda-forge/noarch
I see my package here with version 0.7.53 https://anaconda.org/conda-forge/cliche
but here it still shows 0.7.52 https://conda.anaconda.org/conda-forge/noarch
Hey, I would like to share an article about rhumba available on Windows! Rhumba is
mamba bindings in R
Is there a way to find out what packages in an environment are being held back by dependencies of other packages? ie for packages in an environment which packages can not be updated to their latest version because other packages depend on a lower version and which packages are those?
I noticed that the anaconda.org API sometimes returns huge results for packages with a lot of release files. For example, https://api.anaconda.org/package/conda-forge/dvc is 13 MB. (This is breaking some conda-forge shields/badges due to a 10 MB limit, see conda-forge/dvc-feedstock#215 ). I wanted to see if I could add some more endpoints like
/packages/{owner_login}/{package_name}/latest-version, /packages/{owner_login}/{package_name}/total-downloads, /packages/{owner_login}/{package_name}/platforms, and /packages/{owner_login}/{package_name}/license. Unfortunately I don't see any repository where I could make a PR. Is there any other way to move forward on this? Thanks!
1 reply
conda-build seems to silently fail to upload packages in some cases (cf. logs here, where upload seems to have been successful, although the corresponding packages are not up on anaconda.org: https://app.circleci.com/pipelines/github/facebookresearch/faiss/1733/workflows/da337f45-0d76-4d83-aa03-a3b82a1d4664/jobs/6705). Any ideas?
Does anyone else have experience with this error
ERROR: Directory '.' is not installable. Neither 'setup.py' nor 'pyproject.toml' found. I'm working on a recipe for stylegan2 https://github.com/conda-forge/staged-recipes/pull/15227/checks
hi guys. I don't know where to report an issue with the conda package for click, which is missing from the main/win-64 channel and as a result fails to install colorama, which is a critical dependency on windows. the recipe in conda-forge is fine and the win-64 version is available, but by default most people have main as a priority
>conda create -n clk -c main click
Collecting package metadata (current_repodata.json): done
Solving environment: done
## Package Plan ##
environment location: C:\Users\volex\AppData\Local\Continuum\anaconda3\envs\clk
added / updated specs:
- click
The following packages will be downloaded:
package | build
---------------------------|-----------------
certifi-2021.5.30 | py37haa95532_0 142 KB main
click-8.0.1 | pyhd3eb1b0_0 74 KB main
importlib-metadata-3.10.0 | py37haa95532_0 33 KB main
pip-21.1.2 | py37haa95532_0 2.0 MB main
python-3.7.1 | h33f27b4_4 19.4 MB main
setuptools-52.0.0 | py37haa95532_0 936 KB main
typing_extensions-3.7.4.3 | pyha847dfd_0 25 KB main
vc-14.2 | h21ff451_1 8 KB main
vs2015_runtime-14.27.29016 | h5e58377_2 2.2 MB main
wheel-0.36.2 | pyhd3eb1b0_0 31 KB main
wincertstore-0.2 | py37_0 13 KB main
zipp-3.4.1 | pyhd3eb1b0_0 15 KB main
------------------------------------------------------------
Total: 24.9 MB
The following NEW packages will be INSTALLED:
certifi main/win-64::certifi-2021.5.30-py37haa95532_0
click main/noarch::click-8.0.1-pyhd3eb1b0_0
importlib-metadata main/win-64::importlib-metadata-3.10.0-py37haa95532_0
pip main/win-64::pip-21.1.2-py37haa95532_0
python main/win-64::python-3.7.1-h33f27b4_4
setuptools main/win-64::setuptools-52.0.0-py37haa95532_0
typing_extensions main/noarch::typing_extensions-3.7.4.3-pyha847dfd_0
vc main/win-64::vc-14.2-h21ff451_1
vs2015_runtime main/win-64::vs2015_runtime-14.27.29016-h5e58377_2
wheel main/noarch::wheel-0.36.2-pyhd3eb1b0_0
wincertstore main/win-64::wincertstore-0.2-py37_0
zipp main/noarch::zipp-3.4.1-pyhd3eb1b0_0
when using the conda-forge channel the win-64 version is found an colorama will be installed
>conda create -n clk -c conda-forge click
Collecting package metadata (current_repodata.json): done
Solving environment: done
## Package Plan ##
environment location: C:\Users\volex\AppData\Local\Continuum\anaconda3\envs\clk
added / updated specs:
- click
The following packages will be downloaded:
package | build
---------------------------|-----------------
ca-certificates-2021.5.30 | h5b45459_0 171 KB conda-forge
certifi-2021.5.30 | py39hcbf5309_0 142 KB conda-forge
click-8.0.1 | py39hcbf5309_0 147 KB conda-forge
colorama-0.4.4 | pyh9f0ad1d_0 18 KB conda-forge
openssl-1.1.1k | h8ffe710_0 5.7 MB conda-forge
pip-21.1.2 | pyhd8ed1ab_0 1.1 MB conda-forge
python-3.9.4 |h7840368_0_cpython 19.9 MB conda-forge
setuptools-49.6.0 | py39hcbf5309_3 954 KB conda-forge
sqlite-3.35.5 | h8ffe710_0 1.2 MB conda-forge
vc-14.2 | hb210afc_4 13 KB conda-forge
wheel-0.36.2 | pyhd3deb0d_0 31 KB conda-forge
wincertstore-0.2 |py39hcbf5309_1006 15 KB conda-forge
------------------------------------------------------------
Total: 29.3 MB
The following NEW packages will be INSTALLED:
ca-certificates conda-forge/win-64::ca-certificates-2021.5.30-h5b45459_0
certifi conda-forge/win-64::certifi-2021.5.30-py39hcbf5309_0
click conda-forge/win-64::click-8.0.1-py39hcbf5309_0
colorama conda-forge/noarch::colorama-0.4.4-pyh9f0ad1d_0
openssl conda-forge/win-64::openssl-1.1.1k-h8ffe710_0
pip conda-forge/noarch::pip-21.1.2-pyhd8ed1ab_0
python conda-forge/win-64::python-3.9.4-h7840368_0_cpython
python_abi conda-forge/win-64::python_abi-3.9-1_cp39
setuptools conda-forge/win-64::setuptools-49.6.0-py39hcbf5309_3
sqlite conda-forge/win-64::sqlite-3.35.5-h8ffe710_0
tzdata conda-forge/noarch::tzdata-2021a-he74cb21_0
vc conda-forge/win-64::vc-14.2-hb210afc_4
vs2015_runtime conda-forge/win-64::vs2015_runtime-14.28.29325-h5e1d092_4
wheel conda-forge/noarch::wheel-0.36.2-pyhd3deb0d_0
wincertstore conda-forge/win-64::wincertstore-0.2-py39hcbf5309_1006
Is there any way to use
conda.cli.python_api to create an environment from a yml file? I can't figure out the syntax to get conda env create -f environment.yml to work.run_command(Commands.CREATE, '--file', yml_file, '--prefix', env_path) complains that conda.exceptions.CondaValueError: could not parse 'name: {env name}' in: {yml path}.