ACP ACP Conda Build & Distribution 3

Question 1

What command renders the final meta.yaml for a recipe after applying all variant substitutions, without actually building it?

Accepted Answer

conda render

Answer

`conda render` processes all Jinja2 templating and variant configs in a recipe and outputs the fully resolved meta.yaml without triggering a build.

Question 2

In conda packaging terminology, what is a 'noarch' package?

Accepted Answer

A platform-independent package that installs on any OS/architecture

Answer

A `noarch` package (typically `noarch: python`) contains no compiled binaries and can be installed on any platform, eliminating the need to build per-OS variants.

Question 3

Which command checks a built conda package for common packaging issues such as missing files or incorrect metadata?

Accepted Answer

conda inspect

Answer

`conda inspect` provides subcommands like `conda inspect linkages` and `conda inspect objects` to audit installed packages for linking issues and metadata correctness.

Question 4

When a conda package recipe uses `{{ version }}` in meta.yaml, where is the value of `version` typically sourced from?

Accepted Answer

From a set statement at the top of meta.yaml using Jinja2 templating

Answer

Jinja2 `{% set version = '1.2.3' %}` at the top of meta.yaml assigns the variable, which is then referenced as `{{ version }}` throughout the recipe for DRY versioning.

Question 5

What is the role of the `source` section in a conda meta.yaml recipe?

Accepted Answer

Specifies where to fetch the package source code (URL, git repo, or local path)

Answer

The `source` section tells conda-build where to download or copy the package source, supporting URLs with checksums, git repositories, and local directory paths.

(ACP) Anaconda Certified Professional Practice Test

(ACP) Anaconda Certified Professional Practice Test

ACP ACP Conda Build & Distribution 3