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": "build_number": 1, "depends": [ "depend > 1.1.1" ], "license": "BSD 3-Clause", "name": "fun-packge", "platform": "linux", "subdir": "linux-64", "timestamp": 1535416612069, "version": "0.0.0" } • paths.json

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": "build_number": 1, "depends": [ "depend > 1.1.1" ], "license": "BSD 3-Clause", "name": "fun-packge", "platform": "linux", "subdir": "linux-64", "timestamp": 1535416612069, "version": "0.0.0" } • paths.json

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": "build_number": 1, "depends": [ "depend > 1.1.1" ], "license": "BSD 3-Clause", "name": "fun-packge", "platform": "linux", "subdir": "linux-64", "timestamp": 1535416612069, "version": "0.0.0" } • paths.json

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 explicit spec file is not usually cross platform, and therefore has a comment at the top such as # platform: osx-64 showing the platform where it was created. This platform is the one where this spec file is

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": "build_number": 1, "depends": [ "depend > 1.1.1" ], "license": "BSD 3-Clause", "name": "fun-packge", "platform": "linux", "subdir": "linux-64", "timestamp": 1535416612069, "version": "0.0.0" } • paths.json

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 env create commands. See --subdir, --platform in conda create for more information about allowed values. For example, a user running macOS on the Apple Silicon platform might want to create a python environment

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 env create commands. See --subdir, --platform in conda create for more information about allowed values. For example, a user running macOS on the Apple Silicon platform might want to create a python environment

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 env create commands. See --subdir, --platform in conda create for more information about allowed values. For example, a user running macOS on the Apple Silicon platform might want to create a python environment

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 explicit spec file is not usually cross platform, and therefore has a comment at the top such as # platform: osx-64 showing the platform where it was created. This platform is the one where this spec file is

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 explicit spec file is not usually cross platform, and therefore has a comment at the top such as # platform: osx-64 showing the platform where it was created. This platform is the one where this spec file is