Chapter 4. Contributors welcome conda, Release 25.1.2.dev1 An 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 Environments � Tip Name your export file after your environment to preserve your environment name. cross-platform compatible conda export --from-history>ENV.yml platform + package specific conda export raised. (#12201) • Virtual packages follow context.subdir instead of platform.system() to enable cross-platform installa- tions. (#12219) • Don’t export __glibc virtual package when CONDA_OVERRIDE_GLIBC=""

Chapter 4. Contributors welcome conda, Release 24.11.3.dev2 An 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 Environments � Tip Name your export file after your environment to preserve your environment name. cross-platform compatible conda export --from-history>ENV.yml platform + package specific conda export raised. (#12201) • Virtual packages follow context.subdir instead of platform.system() to enable cross-platform installa- tions. (#12219) • Don’t export __glibc virtual package when CONDA_OVERRIDE_GLIBC=""

Chapter 4. Contributors welcome conda, Release 24.9.3.dev1 An 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 Environments � Tip Name your export file after your environment to preserve your environment name. cross-platform compatible conda export --from-history>ENV.yml platform + package specific conda export raised. (#12201) • Virtual packages follow context.subdir instead of platform.system() to enable cross-platform installa- tions. (#12219) • Don’t export __glibc virtual package when CONDA_OVERRIDE_GLIBC=""

the filename or replace it with a filename of your choice. An 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 Environments � Tip Name your export file after your environment to preserve your environment name. cross-platform compatible conda export --from-history>ENV.yml platform + package specific conda export raised. (#12201) • Virtual packages follow context.subdir instead of platform.system() to enable cross-platform installa- tions. (#12219) • Don’t export __glibc virtual package when CONDA_OVERRIDE_GLIBC=""

the filename or replace it with a filename of your choice. An 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 raised. (#12201) • Virtual packages follow context.subdir instead of platform.system() to enable cross-platform installa- tions. (#12219) • Don’t export __glibc virtual package when CONDA_OVERRIDE_GLIBC="" where compilers and other build tools are installed, separate from the host environment to support cross-compilation. • Host environment: where build-time dependencies are installed, together with the package

the filename or replace it with a filename of your choice. An 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 where compilers and other build tools are installed, separate from the host environment to support cross-compilation. • Host environment: where build-time dependencies are installed, together with the package execute(progress_update_callback=None) reverse() cleanup() __str__() Return str(self). portability Tools for cross-OS portability. Functions update_prefix(path, new_prefix[, placeholder, mode, ...]) replace_prefix(→

the filename or replace it with a filename of your choice. An 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 raised. (#12201) • Virtual packages follow context.subdir instead of platform.system() to enable cross-platform installa- tions. (#12219) • Don’t export __glibc virtual package when CONDA_OVERRIDE_GLIBC="" where compilers and other build tools are installed, separate from the host environment to support cross-compilation. • Host environment: where build-time dependencies are installed, together with the package

the filename or replace it with a filename of your choice. An 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 raised. (#12201) • Virtual packages follow context.subdir instead of platform.system() to enable cross-platform installa- tions. (#12219) • Don’t export __glibc virtual package when CONDA_OVERRIDE_GLIBC="" where compilers and other build tools are installed, separate from the host environment to support cross-compilation. • Host environment: where build-time dependencies are installed, together with the package

the filename or replace it with a filename of your choice. An 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 raised. (#12201) • Virtual packages follow context.subdir instead of platform.system() to enable cross-platform installa- tions. (#12219) • Don’t export __glibc virtual package when CONDA_OVERRIDE_GLIBC="" where compilers and other build tools are installed, separate from the host environment to support cross-compilation. • Host environment: where build-time dependencies are installed, together with the package

the filename or replace it with a filename of your choice. An 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 raised. (#12201) • Virtual packages follow context.subdir instead of platform.system() to enable cross-platform installa- tions. (#12219) • Don’t export __glibc virtual package when CONDA_OVERRIDE_GLIBC="" where compilers and other build tools are installed, separate from the host environment to support cross-compilation. • Host environment: where build-time dependencies are installed, together with the package