envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 1. Conda can no longer find experimenting with approaches that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage tmp_channel instead. (#14243) • Mark conda.testing.context_aware_monkeypatch as pending deprecation. Use conda.testing. fixtures.context_aware_monkeypatch instead. (#14243) • Mark conda.testing.tmp_pkgs_dir

envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 1. Conda can no longer find experimenting with approaches that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage tmp_channel instead. (#14243) • Mark conda.testing.context_aware_monkeypatch as pending deprecation. Use conda.testing. fixtures.context_aware_monkeypatch instead. (#14243) • Mark conda.testing.tmp_pkgs_dir

envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 1. Conda can no longer find experimenting with approaches that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage tmp_channel instead. (#14243) • Mark conda.testing.context_aware_monkeypatch as pending deprecation. Use conda.testing. fixtures.context_aware_monkeypatch instead. (#14243) • Mark conda.testing.tmp_pkgs_dir

envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 1. Conda can no longer find Release 24.1.2.dev2 that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage _BOUND_DELTAS _FLOAT_PATTERN _PARSE_TD_RE _PARSE_TD_KW_MAP parse_td ZERO HOUR UTC EPOCH_AWARE EPOCH_NAIVE LocalTZ DSTSTART_2007 DSTEND_2007 DSTSTART_1987_2006 DSTEND_1987_2006 DSTSTART_1967_1986

different in Windows 10. Installing on macOS Caution: If you use the .pkg installer for Miniconda, be aware that those installers may skip the Destination Select page which will cause the installation to fail envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 76 Chapter 4. Contributors experimenting with approaches that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage

Release 23.7.4.dev7 Installing on macOS Caution: If you use the .pkg installer for Miniconda, be aware that those installers may skip the Destination Select page which will cause the installation to fail envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 1. Conda can no longer find experimenting with approaches that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage

different in Windows 10. Installing on macOS Caution: If you use the .pkg installer for Miniconda, be aware that those installers may skip the Destination Select page which will cause the installation to fail envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 76 Chapter 4. Contributors experimenting with approaches that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage

Release 23.9.1.dev1 Installing on macOS Caution: If you use the .pkg installer for Miniconda, be aware that those installers may skip the Destination Select page which will cause the installation to fail envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 1. Conda can no longer find experimenting with approaches that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage

envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 1. Conda can no longer find Release 24.3.1.dev2 that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage instance. tmp_channel(→ TmpChannelFixture) Fixture returning TmpChannelFixture instance. context_aware_monkeypatch(→ pytest.MonkeyPatch) A monkeypatch fixture that resets context after each test tmp_pkgs_dir(→

envs folder, you’ll have to give each environment a different name. There are a few things to be aware of when placing conda environments outside of the default envs folder. 1. Conda can no longer find Release 24.3.1.dev7 that will allow our executables to be less dependent on PATH and more self-aware of their needed library load paths. For now, though, the only solutions to this problem are to manage instance. tmp_channel(→ TmpChannelFixture) Fixture returning TmpChannelFixture instance. context_aware_monkeypatch(→ pytest.MonkeyPatch) A monkeypatch fixture that resets context after each test tmp_pkgs_dir(→