Environment management with conda and pip in MLOps - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

Conda environment creation output

What is the output when you run the following command in a terminal?

conda create -n myenv python=3.9

MLOps

conda create -n myenv python=3.9

A Usage: conda create [OPTIONS]\nTry 'conda create --help' for more information.

B Error: unknown command 'create-env'\nTry 'conda --help' for more information.

C CommandNotFoundError: No command 'conda create' found.

D Collecting package metadata (current_repodata.json): done\nSolving environment: done\n\n## Package Plan ##\n\n environment location: /home/user/miniconda3/envs/myenv\n\n added / updated specs:\n - python=3.9\n\nThe following packages will be downloaded:\n ...\nProceed ([y]/n)?

💡 Hint

Think about what conda normally outputs when creating an environment.

The 'conda create' command outputs metadata collection, environment solving, and package plan details before asking for confirmation.

🧠 Conceptual

intermediate

Difference between pip and conda for package installation

Which statement correctly describes a key difference between pip and conda when managing Python packages?

A conda installs packages only from PyPI, while pip can install from any URL or local file.

B pip manages virtual environments, but conda does not support environment management.

C pip installs packages only from the Python Package Index (PyPI), while conda can install packages from multiple sources including non-Python libraries.

D conda installs packages only for Python 2, while pip supports Python 3.

💡 Hint

Think about the scope of packages each tool can handle.

Conda can install packages beyond Python libraries, including system-level dependencies, while pip focuses on Python packages from PyPI.

❓ Troubleshoot

advanced

Resolving package conflicts in conda environment

You run conda install numpy=1.18 pandas=1.3 in an existing environment and get a conflict error. What is the best next step to resolve this?

A Run <code>conda update --all</code> to update all packages and resolve conflicts automatically.

B Delete the environment and create a new one with the desired packages from scratch.

C Use <code>pip install numpy==1.18 pandas==1.3</code> inside the conda environment to bypass conda conflicts.

D Ignore the error and force install with <code>conda install --force numpy=1.18 pandas=1.3</code>.

💡 Hint

Think about how conda manages package versions and dependencies.

Updating all packages helps conda find compatible versions and resolve conflicts safely.

🔀 Workflow

advanced

Best practice for sharing environment setup

You want to share your conda environment setup with a teammate so they can recreate it exactly. Which command should you run to export the environment configuration?

A conda list --export > packages.txt

B conda env export --no-builds > environment.yml

C pip freeze > requirements.txt

D pip list --format=freeze > environment.yml

💡 Hint

Consider which command exports a full environment including dependencies and versions.

The 'conda env export' command creates a YAML file with all packages and versions, ideal for sharing environments.

✅ Best Practice

expert

Combining pip and conda in environment management

You have a conda environment but need to install a package only available via pip. What is the recommended best practice to avoid dependency issues?

A First install all conda packages, then install pip packages inside the activated conda environment using pip.

B Install pip packages first, then create the conda environment with conda packages.

C Use pip outside the conda environment to install packages globally, then activate conda environment.

D Mix pip and conda installs randomly without activating the environment.

💡 Hint

Think about environment isolation and dependency management order.

Installing conda packages first ensures dependency resolution; pip installs afterward add packages not available in conda.

Practice

1. What is the main purpose of using conda create -n myenv python=3.8?

easy

A. To delete the environment named 'myenv' and install Python 3.8 globally

B. To update Python to version 3.8 in the current environment

C. To create a new isolated environment named 'myenv' with Python 3.8 installed

D. To install all packages listed in a file named 'myenv' with Python 3.8

Solution

1. Step 1: Understand the conda create command

   This command is used to create a new environment in conda, isolating packages and Python versions.

2. Step 2: Analyze the flags and arguments

   The -n myenv specifies the environment name, and python=3.8 sets the Python version inside it.

3. Final Answer:

   To create a new isolated environment named 'myenv' with Python 3.8 installed -> Option C

4. Quick Check:

   conda create -n myenv python=3.8 = D [OK]

Hint: Remember: 'conda create -n' makes new isolated envs [OK]

Common Mistakes:

• Confusing 'create' with 'install' or 'update'
• Thinking it affects the global Python installation
• Misunderstanding the '-n' flag as package name

2. Which of the following commands correctly activates a conda environment named dataenv?

easy

A. activate conda dataenv

B. conda activate dataenv

C. conda start dataenv

D. source deactivate dataenv

Solution

1. Step 1: Recall the syntax to activate conda environments

   The correct command to activate an environment is conda activate <env_name>.

2. Step 2: Check each option

   conda activate dataenv matches the correct syntax. Options B, C, and D use incorrect command order or wrong commands.

3. Final Answer:

   conda activate dataenv -> Option B

4. Quick Check:

   Activate env = conda activate env_name [OK]

Hint: Use 'conda activate env_name' to switch environments [OK]

Common Mistakes:

• Using 'activate conda' instead of 'conda activate'
• Confusing 'source deactivate' with activation
• Trying 'conda start' which is invalid

3. Given the following commands run in order:

conda create -n testenv python=3.9 -y
conda activate testenv
pip install numpy
pip list | grep numpy

What will be the output of the last command?

medium

A. numpy with its installed version number

B. No output because pip list does not work inside conda

C. Error: 'pip' command not found

D. List of all packages except numpy

Solution

1. Step 1: Understand environment creation and activation

   The environment 'testenv' is created with Python 3.9 and then activated, so all commands run inside it.

2. Step 2: Installing numpy with pip inside the active environment

   Running pip install numpy installs numpy in 'testenv'. The pip list | grep numpy command will show numpy and its version.

3. Final Answer:

   numpy with its installed version number -> Option A

4. Quick Check:

   pip install inside active env = numpy listed [OK]

Hint: pip installs packages in active conda env, visible with pip list [OK]

Common Mistakes:

• Thinking pip installs globally ignoring conda env
• Assuming pip commands fail inside conda
• Expecting no output from pip list

4. You run conda activate myenv but get the error: CommandNotFoundError: Your shell has not been properly configured to use 'conda activate'. What is the most likely fix?

medium

A. Reinstall Python globally on your system

B. Deactivate any active environment before activating 'myenv'

C. Use pip install conda to fix the error

D. Run conda init to configure your shell, then restart the terminal

Solution

1. Step 1: Understand the error cause

   This error means the shell does not know how to run conda activate because it lacks proper initialization.

2. Step 2: Apply the fix by initializing conda for the shell

   Running conda init sets up the shell scripts needed. Restarting the terminal applies changes.

3. Final Answer:

   Run conda init to configure your shell, then restart the terminal -> Option D

4. Quick Check:

   Shell config for conda = conda init + restart [OK]

Hint: Run 'conda init' once after install, then restart terminal [OK]

Common Mistakes:

• Trying to reinstall Python instead of fixing shell config
• Using pip to install conda which is incorrect
• Ignoring the need to restart terminal after init

5. You want to create a reproducible environment for a project using conda and pip. Which sequence of commands correctly creates an environment, installs packages from a requirements.txt file using pip, and exports the environment including pip packages?

hard

A. conda create -n projenv python=3.10 -y && conda activate projenv && pip install -r requirements.txt && conda env export > environment.yml

B. conda create -n projenv python=3.10 -y && pip install -r requirements.txt && conda activate projenv && conda env export > environment.yml

C. conda create -n projenv python=3.10 -y && conda activate projenv && pip install -r requirements.txt && conda env export --from-history > environment.yml

D. conda activate projenv && conda create -n projenv python=3.10 -y && pip install -r requirements.txt && conda env export > environment.yml

Solution

1. Step 1: Create and activate the environment before installing packages

   You must first create the environment, then activate it to install packages inside it.

2. Step 2: Install pip packages and export full environment

   After activation, install packages from requirements.txt using pip. Then export the full environment including pip packages with conda env export.

3. Final Answer:

   conda create -n projenv python=3.10 -y && conda activate projenv && pip install -r requirements.txt && conda env export > environment.yml -> Option A

4. Quick Check:

   Create, activate, pip install, export full env = C [OK]

Hint: Activate env before pip install; export full env to include pip packages [OK]

Common Mistakes:

• Installing pip packages before activating environment
• Using --from-history which excludes pip packages
• Activating environment after installing packages