com/AnacondaRecipes/intel_repack-feedstock/blob/ e699b12/recipe/meta.yaml#L108-L112 Note that mkl is a string of blas. That metapackage is automatically added as a dependency using run_exports when someone the mutual exclusivity. It unifies the options on a single package name, but with a different build string. Automating the addition of the metapackage with run_exports helps ensure the library consumers (package 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 BLAS, so using the metapackage

0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 Note this also returned “numpydoc” as it contains the string “numpy”. To get a more specific result set you can add < and >. Updating packages Use conda update connection's normal security and is not recommended: ssl_verify: False You can also set ssl_verify to a string path to a certificate, which can be used to verify SSL connections: ssl_verify: corp.crt 56 Chapter utilize conda-build 3's build matrices with a build configuration that is not reflected in the build string, packages will be missing due to clobbering. no_verify: Disable recipe and package verification

com/AnacondaRecipes/intel_repack-feedstock/blob/ e699b12/recipe/meta.yaml#L108-L112 Note that mkl is a string of blas. That metapackage is automatically added as a dependency using run_exports when someone the mutual exclusivity. It unifies the options on a single package name, but with a different build string. Automating the addition of the metapackage with run_exports helps ensure the library consumers (package 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 BLAS, so using the metapackage

0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 Note this also returned “numpydoc” as it contains the string “numpy”. To get a more specific result set you can add < and >. Updating packages Use conda update connection's normal security and is not recommended: ssl_verify: False You can also set ssl_verify to a string path to a certificate, which can be used to verify SSL connections: ssl_verify: corp.crt offline: utilize conda-build 3's build matrices with a build configuration that is not reflected in the build string, packages will be missing due to clobbering. no_verify: Disable recipe and package verification

0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 Note this also returned “numpydoc” as it contains the string “numpy”. To get a more specific result set you can add < and >. Updating packages Use conda update by setting ssl_verify to "truststore": ssl_verify: truststore You can also set ssl_verify to a string path to a certificate, which can be used to verify SSL connections: ssl_verify: corp.crt offline: utilize conda-build 3's build matrices with a build configuration that is not reflected in the build string, packages will be missing due to clobbering. no_verify: Disable recipe and package verification

com/AnacondaRecipes/intel_repack-feedstock/blob/ e699b12/recipe/meta.yaml#L108-L112 Note that mkl is a string of blas. That metapackage is automatically added as a dependency using run_exports when someone the mutual exclusivity. It unifies the options on a single package name, but with a different build string. Automating the addition of the metapackage with run_exports helps ensure the library consumers (package 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 BLAS, so using the metapackage

com/AnacondaRecipes/intel_repack-feedstock/blob/ e699b12/recipe/meta.yaml#L108-L112 Note that mkl is a string of blas. That metapackage is automatically added as a dependency using run_exports when someone the mutual exclusivity. It unifies the options on a single package name, but with a different build string. Automating the addition of the metapackage with run_exports helps ensure the library consumers (package 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 BLAS, so using the metapackage

0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 Note this also returned “numpydoc” as it contains the string “numpy”. To get a more specific result set you can add < and >. Updating packages Use conda update connection's normal security and is not recommended: ssl_verify: False You can also set ssl_verify to a string path to a certificate, which can be used to verify SSL connections: ssl_verify: corp.crt 56 Chapter utilize conda-build 3's build matrices with a build configuration that is not reflected in the build string, packages will be missing due to clobbering. no_verify: Disable recipe and package verification

0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 Note this also returned “numpydoc” as it contains the string “numpy”. To get a more specific result set you can add < and >. Updating packages Use conda update connection's normal security and is not recommended: ssl_verify: False You can also set ssl_verify to a string path to a certificate, which can be used to verify SSL connections: ssl_verify: corp.crt 56 Chapter utilize conda-build 3's build matrices with a build configuration that is not reflected in the build string, packages will be missing due to clobbering. no_verify: Disable recipe and package verification

0-np111py36_0/info/index.json: numpy 1.11.3␣ ˓→py36_0 Note this also returned “numpydoc” as it contains the string “numpy”. To get a more specific result set you can add < and >. Updating packages Use conda update by setting ssl_verify to "truststore": ssl_verify: truststore You can also set ssl_verify to a string path to a certificate, which can be used to verify SSL connections: ssl_verify: corp.crt offline: utilize conda-build 3's build matrices with a build configuration that is not reflected in the build string, packages will be missing due to clobbering. no_verify: Disable recipe and package verification