← The Forge
Fundamentals Lab · Toward FireSDK 2

Python Environments & Packages

Picking up exactly where the Git lab left off — the FireSDK clone on disk. This lab installs it for real, the same way you'd install it to actually test it, then proves it's isolated by breaking it on purpose.
Before We Start

Why bother isolating anything?

  • A virtual environment (venv) is a private, disposable copy of Python for one project — so installing a package here can't collide with or break any other project on the machine.
  • Once you activate one, your prompt itself changes to show it — watch for (.venv) appearing at the front of the prompt below, that's your confirmation it's on.
  • Same terminal as before — click in, type.
Done

Isolated, editable, and now on your PATH.

A venv means this project's dependencies can't collide with any other project's. -e means editing the SDK's source shows up immediately, no reinstall. That's exactly the setup FireSDK's own README asks for. The next lesson is the payoff: you have a working install, a real token, and a real API to call.
1 / 1
ends with a "mark complete" step