wildcards Let's say you are working on a project that requires version 2.3 of a package. If you upgrade to 2.4 or 3.0, your project will break. You're also using an environment file to create your environment inside a Docker container. It is recommended to use this installation in a read-only manner and upgrade conda using the respective package manager only. If you’re new to conda, check out the documentation • Install as many requirements as possible with conda then use pip. • Pip should be run with --upgrade-strategy only-if-needed (the default). • Do not use pip with the --user argument, avoid all users

wildcards Let's say you are working on a project that requires version 2.3 of a package. If you upgrade to 2.4 or 3.0, your project will break. You're also using an environment file to create your environment inside a Docker container. It is recommended to use this installation in a read-only manner and upgrade conda using the respective package manager only. If you’re new to conda, check out the documentation • Install as many requirements as possible with conda then use pip. • Pip should be run with --upgrade-strategy only-if-needed (the default). • Do not use pip with the --user argument, avoid all users

5.2 Contributors • @kalefranz 5.6 4.5.7 (2018-07-09) 5.6.1 Improvements • resolve #7423 add upgrade error for unsupported repodata_version (#7415) • raise CondaUpgradeError for conda version downgrades environment due to EACCES (#6752) 5.18 4.4.7 (2018-01-08) 5.18.1 Improvements • resolve #6650 add upgrade message for unicode errors in python 2 (#6651) 5.18.2 Bug Fixes • fix #6643 difference between handler for ‘conda activate’ (4.4.0rc2) (#6365) • fix #6173 double prompt immediately after conda 4.4 upgrade (4.4.0rc2) (#6351) • fix #6181 keep existing pythons pinned to minor version (4.4.0rc2) (#6363)

5.2 Contributors • @kalefranz 5.6 4.5.7 (2018-07-09) 5.6.1 Improvements • resolve #7423 add upgrade error for unsupported repodata_version (#7415) • raise CondaUpgradeError for conda version downgrades environment due to EACCES (#6752) 5.18 4.4.7 (2018-01-08) 5.18.1 Improvements • resolve #6650 add upgrade message for unicode errors in python 2 (#6651) 5.18.2 Bug Fixes • fix #6643 difference between handler for ‘conda activate’ (4.4.0rc2) (#6365) • fix #6173 double prompt immediately after conda 4.4 upgrade (4.4.0rc2) (#6351) • fix #6181 keep existing pythons pinned to minor version (4.4.0rc2) (#6363)

wildcards Let's say you are working on a project that requires version 2.3 of a package. If you upgrade to 2.4 or 3.0, your project will break. You're also using an environment file to create your environment inside a Docker container. It is recommended to use this installation in a read-only manner and upgrade conda using the respective package manager only. If you’re new to conda, check out the documentation • Install as many requirements as possible with conda then use pip. • Pip should be run with --upgrade-strategy only-if-needed (the default). • Do not use pip with the --user argument, avoid all users

wildcards Let's say you are working on a project that requires version 2.3 of a package. If you upgrade to 2.4 or 3.0, your project will break. You're also using an environment file to create your environment inside a Docker container. It is recommended to use this installation in a read-only manner and upgrade conda using the respective package manager only. If you’re new to conda, check out the documentation • Install as many requirements as possible with conda then use pip. • Pip should be run with --upgrade-strategy only-if-needed (the default). • Do not use pip with the --user argument, avoid all users

wildcards Let's say you are working on a project that requires version 2.3 of a package. If you upgrade to 2.4 or 3.0, your project will break. You're also using an environment file to create your environment inside a Docker container. It is recommended to use this installation in a read-only manner and upgrade conda using the respective package manager only. If you’re new to conda, check out the documentation • Install as many requirements as possible with conda then use pip. • Pip should be run with --upgrade-strategy only-if-needed (the default). 82 Chapter 4. Contributors welcome conda, Release 23.10

wildcards Let's say you are working on a project that requires version 2.3 of a package. If you upgrade to 2.4 or 3.0, your project will break. You're also using an environment file to create your environment inside a Docker container. It is recommended to use this installation in a read-only manner and upgrade conda using the respective package manager only. If you’re new to conda, check out the documentation • Install as many requirements as possible with conda then use pip. • Pip should be run with --upgrade-strategy only-if-needed (the default). 82 Chapter 4. Contributors welcome conda, Release 23.11

Docker container. Tip It is recommended to use this installation method in a read-only manner and upgrade conda using the respective package manager only. 20 Chapter 4. Contributors welcome conda, Release • Install as many requirements as possible with conda then use pip. • Pip should be run with --upgrade-strategy only-if-needed (the default). 4.1. User guide 29 conda, Release 24.1.2.dev2 • Do not wildcards Let's say you are working on a project that requires version 2.3 of a package. If you upgrade to 2.4 or 3.0, your project will break. You're also using an environment file to create your environment

Docker container. Tip It is recommended to use this installation method in a read-only manner and upgrade conda using the respective package manager only. 20 Chapter 4. Contributors welcome conda, Release • Install as many requirements as possible with conda then use pip. • Pip should be run with --upgrade-strategy only-if-needed (the default). 4.1. User guide 29 conda, Release 24.3.1.dev2 • Do not wildcards Let's say you are working on a project that requires version 2.3 of a package. If you upgrade to 2.4 or 3.0, your project will break. You're also using an environment file to create your environment