Skip to content
China Explained

Installation and Environment

Installation and Environment

Section titled “Installation and Environment”

Create a clean environment

Section titled “Create a clean environment”
Terminal window
python3 --version
python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
pip install swarms
python -m pip show swarms

The current package metadata checked for this site lists swarms 12.0.0 with Python >=3.10,<4.0. Recheck before serious use, and record the package version, provider, operating system, and first successful command.

Keep setup problems separated

Section titled “Keep setup problems separated”
  • Prove the command works before debugging provider keys.
  • Do not mix tools, memory, gateways, and deployment into the install problem.
  • Review installer source before using it on production machines.

A clean install is easier to debug

Section titled “A clean install is easier to debug”

Use a fresh shell and a small environment. If install, provider auth, and workflow code all change at once, the first failure has too many possible causes. Keep the first session boring: command visible, package version visible, model call visible.

Terminal window
python3 -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
pip install swarms
python -m pip show swarms
After installWhy it matters
Package version is recordedYou know what future behavior is being compared against.
Python version is recordedMany failures are environment mismatch, not framework behavior.
First command is recordedAnother person can reproduce the starting point.
Provider key is not in codeExamples stay safe to commit.
Section titled “Related pages”

References

Section titled “References”