anything you like. However, multiple packages may create script files, so be sure to use descriptive names that are not used by other packages. One popular option is to give the script a name in the form installed will likely determine the outcome, which may be undesirable. If the two packages have different names, or if you're building variants of packages and need to line up other software in the stack, we recommend available to install, in your terminal window, run: conda search python This lists all packages whose names contain the text python. To list only the packages whose full name is exactly python, add the --full-name

anything you like. However, multiple packages may create script files, so be sure to use descriptive names that are not used by other packages. One popular option is to give the script a name in the form installed will likely determine the outcome, which may be undesirable. If the two packages have different names, or if you're building variants of packages and need to line up other software in the stack, we recommend available to install, in your terminal window, run: conda search python This lists all packages whose names contain the text python. To list only the packages whose full name is exactly python, add the --full-name

anything you like. However, multiple packages may create script files, so be sure to use descriptive names that are not used by other packages. One popular option is to give the script a name in the form installed will likely determine the outcome, which may be undesirable. If the two packages have different names, or if you're building variants of packages and need to line up other software in the stack, we recommend available to install, in your terminal window, run: conda search python This lists all packages whose names contain the text python. To list only the packages whose full name is exactly python, add the --full-name

the introduction of the .conda file format. Note: In conda 4.7 and later, you cannot use package names that end in “.conda” as they conflict with the .conda file format for packages. Using packages • metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at some examples for how to use mutex metapackages to build NumPy against different BLAS chosen. Neither MKL nor its dependencies are mutually exclusive (meaning they do not have similar names and different version/build-string). This pathway may lead to some ambiguity and solutions with mixed

anything you like. However, multiple packages may create script files, so be sure to use descriptive names that are not used by other packages. One popular option is to give the script a name in the form installed will likely determine the outcome, which may be undesirable. If the two packages have different names, or if you're building variants of packages and need to line up other software in the stack, we recommend available to install, in your terminal window, run: conda search python This lists all packages whose names contain the text python. To list only the packages whose full name is exactly python, add the --full-name

the introduction of the .conda file format. Note: In conda 4.7 and later, you cannot use package names that end in “.conda” as they conflict with the .conda file format for packages. Using packages • metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at some examples for how to use mutex metapackages to build NumPy against different BLAS chosen. Neither MKL nor its dependencies are mutually exclusive (meaning they do not have similar names and different version/build-string). This pathway may lead to some ambiguity and solutions with mixed

anything you like. However, multiple packages may create script files, so be sure to use descriptive names that are not used by other packages. One popular option is to give the script a name in the form installed will likely determine the outcome, which may be undesirable. If the two packages have different names, or if you're building variants of packages and need to line up other software in the stack, we recommend available to install, in your terminal window, run: conda search python This lists all packages whose names contain the text python. To list only the packages whose full name is exactly python, add the --full-name

anything you like. However, multiple packages may create script files, so be sure to use descriptive names that are not used by other packages. One popular option is to give the script a name in the form installed will likely determine the outcome, which may be undesirable. If the two packages have different names, or if you're building variants of packages and need to line up other software in the stack, we recommend available to install, in your terminal window, run: conda search python This lists all packages whose names contain the text python. To list only the packages whose full name is exactly python, add the --full-name

the introduction of the .conda file format. Note: In conda 4.7 and later, you cannot use package names that end in “.conda” as they conflict with the .conda file format for packages. Using packages • metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at some examples for how to use mutex metapackages to build NumPy against different BLAS chosen. Neither MKL nor its dependencies are mutually exclusive (meaning they do not have similar names and different version/build-string). This pathway may lead to some ambiguity and solutions with mixed

the introduction of the .conda file format. Note: In conda 4.7 and later, you cannot use package names that end in “.conda” as they conflict with the .conda file format for packages. Using packages • metapackages function as a tool to help achieve mutual exclusivity among packages with different names. Let's look at some examples for how to use mutex metapackages to build NumPy against different BLAS chosen. Neither MKL nor its dependencies are mutually exclusive (meaning they do not have similar names and different version/build-string). This pathway may lead to some ambiguity and solutions with mixed