crosfrench.blogg.se

#' $ conda list -export | awk -v channels="conda-forge,defaults" -f list_export_to_yaml.awk #' $ conda list -export | awk -v no_builds=1 -f list_export_to_yaml.awk #' $ conda list -export | awk -f list_export_to_yaml.awk List_export_to_yaml.awk #!/usr/bin/env awk -f If the environment is no longer around, or the requirements.txt was provided by another user, then another option is to convert the file to a YAML format. Option 3: Convert requirements.txt to YAML Which can recreate (on the same platform) with conda env create -n m1 -f environment.yaml So, if you still have the old environment around, consider using: conda env export > environment.yaml

Option 2: Export YAMLĪlternatively, serializing to YAML can handle both capturing and reinstalling Pip-installed packages. However, this is not always reliable, since some packages go by different names in the two repositories. Sed -e 's/=pypi_0//' requirements.txt > Ĭonda will then try to treat these PyPI package specifications as Conda packages. That is, something like: # remove all PyPI references The quickest fix is probably to edit the file to remove the build string specification on those packages. The conda list -e command captures this info, but the conda create command cannot handle it. The packages likely are in Conda Forge as suggested, but the build strings, " pypi_0", indicate that they had been installed from PyPI in the previous environment. I think the missing packages should be in conda-forge, shouldn´t they? Used Version Why can´t conda find the packages in the channels? PackagesNotFoundError: The following packages are not available from current channels: I created the requirements.txt file with conda list -e > requirements.txt on another computer in the past.