Windows x86 64-bit macOS Miniconda installer for: macOS with Apple Silicon 64-bit macOS with Intel CPU 64-bit Linux Miniconda installer for: Linux x86 64-bit Homebrew Run the following Homebrew command: features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured

features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs Contributors welcome conda, Release 24.3.1.dev2 linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured

features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs Contributors welcome conda, Release 24.3.1.dev7 linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured

features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured

features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z 4.3. Commands 135 conda, Release 23.10.1.dev3 Use packages built for this linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured

features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured linux-armv6l, linux-armv7l, linux-ppc64, linux-ppc64le, linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured

features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs Contributors welcome conda, Release 24.1.2.dev2 linux-riscv64, linux-s390x, osx-64, osx-arm64, win-32, win-64, win-arm64, zos- z Use packages built for this platform. The new environment will be configured launchers for Windows (conda/shell/cli-*.exe) to match the ones found in conda- build. (#11676) • Add win-arm64 as a known platform (subdir). (#11778) 188 Chapter 4. Contributors welcome conda, Release 24.1

features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs tc/conda/activate.d/activate-gfortran_ ˓→osx-arm64.sh" . "/Users/username/.local/anaconda/envs/compilers/etc/conda/activate.d/activate_clang_ ˓→osx-arm64.sh" . "/Users/username/.local/anaconda/envs/ compilers/etc/conda/activate.d/activate_clangxx_ ˓→osx-arm64.sh" Those three lines are sourcing the relevant scripts. Similarly, for deactivation, notice how the deactivation scripts are executed first

features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs tc/conda/activate.d/activate-gfortran_ ˓→osx-arm64.sh" . "/Users/username/.local/anaconda/envs/compilers/etc/conda/activate.d/activate_clang_ ˓→osx-arm64.sh" . "/Users/username/.local/anaconda/envs/ compilers/etc/conda/activate.d/activate_clangxx_ ˓→osx-arm64.sh" Those three lines are sourcing the relevant scripts. Similarly, for deactivation, notice how the deactivation scripts are executed first

features present on the system that cannot be managed directly by conda, like system driver versions or CPU features. Virtual packages are not real packages and not displayed by conda list. Instead conda runs tc/conda/activate.d/activate-gfortran_ ˓→osx-arm64.sh" . "/Users/username/.local/anaconda/envs/compilers/etc/conda/activate.d/activate_clang_ ˓→osx-arm64.sh" . "/Users/username/.local/anaconda/envs/ compilers/etc/conda/activate.d/activate_clangxx_ ˓→osx-arm64.sh" Those three lines are sourcing the relevant scripts. Similarly, for deactivation, notice how the deactivation scripts are executed first