![]() ![]() If this is not sufficient, then there is an external utility called conda-minify that offers some functionality to export an environment that is minimized based on a dependency tree rather than through the user's explicit specifications. How stupid of me I thought > environment.yml was the output, not part of the command. You're looking for conda env export > name-your-env-file-here.yml. These flags work in a mutually exclusive manner. You need to redirect the output to a file. On the other hand, if the user originally included additional constraints beyond version and build they will also be included (e.g., a channel specification conda install conda-forge::numpy will lead to conda-forge::numpy).Īnother option worth noting is the -no-builds flag, which will export every package in the YAML, but leave out the build specifiers. Hence, creating a new environment is very likely not going to use the exact same versions and builds. This will only include versions if the user originally included versions during installation. However, the -name -n flag can be used to override this if you happen to not be that into flowers. The hash is made up from the 'used' variables - if anything is used, you have a hash. Yes, the environment name will be flowerclassifier by default. A hash will appear when the package is affected by one or more variables from the condabuildconfig.yaml file. Have a try: conda env export -from-history -name my_env > myenv.yml The string defaults to the default conda-build string plus the build number. Instead of including exact build info for each package, it will include only what are called explicit specifications, i.e., the specifications that a user has explicitly requested via the CLI (e.g., conda install scipy=1.3.1). This is sort of what the -from-history flag is for, but not exactly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |