alternative to a tarball. The .conda file format consists of an outer, uncompressed ZIP-format container, with 2 inner compressed .tar files. For the .conda format's initial internal compression format multiple different pure Python packages on different architectures and Python versions by sorting out platform and Python version-specific differences at install time. In order to qualify as a noarch Python files in the package (not included in info/) • index.json – metadata about the package including platform, version, dependencies, and build info { "arch": "x86_64", "build": "py37hfa4b5c9_1", "build_number":

alternative to a tarball. The .conda file format consists of an outer, uncompressed ZIP-format container, with 2 inner compressed .tar files. For the .conda format's initial internal compression format multiple different pure Python packages on different architectures and Python versions by sorting out platform and Python version-specific differences at install time. In order to qualify as a noarch Python files in the package (not included in info/) • index.json – metadata about the package including platform, version, dependencies, and build info { "arch": "x86_64", "build": "py37hfa4b5c9_1", "build_number":

conda/envs These RPM and Debian packages also provide another way to set up conda inside a Docker container. � Tip It is recommended to use this installation method in a read-only manner and upgrade conda Specifying a different target platform for an environment By default, conda will create environments targeting the platform it's currently running on. You can check which platform you are currently on by running info and checking the platform entry. However, in some cases you might want to create an environment for a different target platform or architecture. To do so, use the --platform flag available in the

conda/envs These RPM and Debian packages also provide another way to set up conda inside a Docker container. � Tip It is recommended to use this installation method in a read-only manner and upgrade conda explicit specification files to build an identical conda environment on the same operating system platform, either on the same machine or on a different machine. Use the terminal for the following steps: file may be used to create an environment using: # $ conda create --name --file # platform: osx-64 @EXPLICIT https://repo.anaconda.com/pkgs/free/osx-64/mkl-11.3.3-0.tar.bz2 (continues on

conda/envs These RPM and Debian packages also provide another way to set up conda inside a Docker container. Tip It is recommended to use this installation method in a read-only manner and upgrade conda explicit specification files to build an identical conda environment on the same operating system platform, either on the same machine or on a different machine. Use the terminal for the following steps: file may be used to create an environment using: # $ conda create --name --file # platform: osx-64 @EXPLICIT https://repo.anaconda.com/pkgs/free/osx-64/mkl-11.3.3-0.tar.bz2 https://repo.anaconda

conda/envs These RPM and Debian packages also provide another way to set up conda inside a Docker container. Tip It is recommended to use this installation method in a read-only manner and upgrade conda explicit specification files to build an identical conda environment on the same operating system platform, either on the same machine or on a different machine. Use the terminal for the following steps: file may be used to create an environment using: # $ conda create --name --file # platform: osx-64 @EXPLICIT https://repo.anaconda.com/pkgs/free/osx-64/mkl-11.3.3-0.tar.bz2 https://repo.anaconda

conda/envs These RPM and Debian packages also provide another way to set up conda inside a Docker container. Tip It is recommended to use this installation method in a read-only manner and upgrade conda explicit specification files to build an identical conda environment on the same operating system platform, either on the same machine or on a different machine. Use the terminal for the following steps: file may be used to create an environment using: # $ conda create --name --file # platform: osx-64 @EXPLICIT https://repo.anaconda.com/pkgs/free/osx-64/mkl-11.3.3-0.tar.bz2 https://repo.anaconda

alternative to a tarball. The .conda file format consists of an outer, uncompressed ZIP-format container, with 2 inner compressed .tar files. For the .conda format's initial internal compression format multiple different pure Python packages on different architectures and Python versions by sorting out platform and Python version-specific differences at install time. In order to qualify as a noarch Python files in the package (not included in info/) • index.json – metadata about the package including platform, version, dependencies, and build info { "arch": "x86_64", "build": "py37hfa4b5c9_1", "build_number":

conda/envs These RPM and Debian packages also provide another way to set up conda inside a Docker container. Tip It is recommended to use this installation method in a read-only manner and upgrade conda explicit specification files to build an identical conda environment on the same operating system platform, either on the same machine or on a different machine. Use the terminal for the following steps: file may be used to create an environment using: # $ conda create --name --file # platform: osx-64 @EXPLICIT https://repo.anaconda.com/pkgs/free/osx-64/mkl-11.3.3-0.tar.bz2 https://repo.anaconda

alternative to a tarball. The .conda file format consists of an outer, uncompressed ZIP-format container, with 2 inner compressed .tar files. For the .conda format's initial internal compression format multiple different pure Python packages on different architectures and Python versions by sorting out platform and Python version-specific differences at install time. In order to qualify as a noarch Python files in the package (not included in info/) • index.json – metadata about the package including platform, version, dependencies, and build info { "arch": "x86_64", "build": "py37hfa4b5c9_1", "build_number":