L

Dependency installation vs Integration

Install the package and run your script again. The output is identical, byte for byte. Installing changed what is on the machine — it changed nothing about what your program does.

Sort six steps See what each one is

Two terminals. Same green message.

Both say the package installed successfully. Run the script in each and only one of them behaves differently than it did before.

Terminal A

pip install pandas → Successfully installed pandas-2.2.0.

Run the failing script now. Same error, same line, same second. Nothing about it was ever going to change.
Terminal B

Same install, then four lines added to the script: import it, load the file with it, group the rows, write the result.

That edit is the integration. It is where the package stops being a folder on disk and starts being part of what the program does.
Both terminals report success. Only one of them changed what happens when you run anything.

What each one actually is

One changes what is available on the machine. One changes what happens when the code runs.

Installing changes what is on the machine. It changes nothing about what your program does. That is not a subtlety — it is literal: run the same script before and after the install and the output is identical, because nothing in your code has been altered to mention the new thing.

The reason it fools people is that both steps end the same way, with a green line in a terminal and a feeling of progress. One of those green lines means a tool is available. The other would have meant it is being used, and it never appeared.

After any install, run the thing it was supposed to fix. If the behaviour is identical, you are half done — and that is the normal state, not a failure. The remaining half is a change to your own code or workflow that calls it.

Sort six steps, then see what each changes

Tap a step, then tap whether the program behaves differently afterwards. Then see exactly what each one changes.

The same green message, different desk

Pick a situation. In every one, the install succeeded and nothing else did.

In every one of these, the install succeeded and nothing else did.

The report that still failed

The package is there. It is on disk, it imports cleanly, and the script that fails has never once mentioned its name.

Test the distinction

Five questions. Nothing is scored.

Question 1 of 5
Multiple choice

The words this pair actually contains

Five terms, not two. Tap one.

Questions people ask

Open all 10 questions
How do I know if a package is installed or integrated?

Check if the package appears in your environment or list of installed tools. Then, see if your workflow or code actually uses it—run the task and watch for results. Installation alone does not guarantee the tool is active in your process.

Why does my script fail even after installing the required package?

Installation only makes the package available. If your code does not call or connect to the package, nothing changes. Check your script to ensure it imports and uses the package where needed.

What is the difference between pip install and importing a package in code?
  • pip install adds the package to your environment.
  • import brings the package into your script for use.
  • Both are needed for the tool to work in your workflow.
  • Installation without import means the code cannot use the package.
Can I integrate a package without installing it first?

No. Integration relies on the package being present in your environment. Installation is always the first step. Without it, your code cannot find or use the package, and integration fails.

How do I check if integration is working?
  1. Run your workflow or script that should use the package.
  2. Watch for output or results that rely on the package.
  3. Check for errors or missing features.
  4. If the package is called and produces results, integration is working.
Why do people confuse installation with integration?

Both steps happen before you can use a tool, and both may show a success message. On screen, there is little to separate them, but only integration connects the tool to your actual work.

What happens if I update a package but do not update my code?

Your workflow may break or produce errors. New versions can change how packages work, so integration needs checking after any update. Always test your workflow after updating a dependency.

Is installing a package enough to fix a broken workflow?

Not always. Installation only makes the tool available. Your workflow or code must actually use the package, and sometimes you need to change your code to make use of new or fixed features.

How do I avoid missing the integration step?
  • Test your workflow after installing a package.
  • Check your code for import and usage.
  • Ask a colleague to review the changes.
  • Document both installation and integration steps.
What is a real sign that integration has failed?
SymptomWhat it means
No output from the new toolCode is not using the package
Import errorPackage is not installed or not found
Old behaviour after installIntegration step did not happen
Unexpected errorsIntegration or compatibility issue

Available and used are two different states, and a green install message only ever reports the first.

Copyright © Pawan Nayar · LLOS.ai · 2026 — Dependency installation vs Integration: the package is present, versus the package is doing something.Original pedagogy, voice, and design — all rights reserved.