Me kuma yadda ake amfani da sabannin muhallin Python (virtual environments)?

Question

Accepted Answer

A **sabannin muhalli** shine muhallin Python da aka keɓe da jiya, mai niyansa kuɗin saman da aka shiryar, daban da system Python da kuma daban da sauran ayyukan. Yana warware **rikicin alaƙa** — ayyuka daban-daban za su iya amfani da bambaddun (har ma da rashin daidaita) sifofi na paket guda.

## Matsalar da ita take warware

```text
Project A needs Django 3.2
Project B needs Django 4.2
→ Installing globally, they CONFLICT — you can't have both versions system-wide.
Virtual environments give each project its OWN isolated set of packages.
```

A gida karye kasancewa da kashe, shiryar kuɗin saman a duniya gida yana haifar da rashin daidaita sifofi tsakanin ayyuka kuma zai iya karya kayan aiki na tsarin waɗanda ke dogara akan takamaiman sifofi.

## Ƙirƙira da amfani da ɗaya (built-in venv)

```bash
# 1. create a virtual environment (a folder named .venv)
python -m venv .venv

# 2. ACTIVATE it (shell-specific)
source .venv/bin/activate      # macOS/Linux
.venv\Scripts\activate         # Windows

# 3. now pip installs go INTO this env, isolated from the system
pip install django requests

# 4. when done
deactivate
```

Jiya an kunna shi, `python` da `pip` suna nufin muhallin da aka keɓe — kuɗin saman ya shiryar kawai a can, ba a duniya gida ba.

## Ƙayyade da maimaita dogaje

```bash
pip freeze > requirements.txt       # record exact installed versions
pip install -r requirements.txt     # recreate the env elsewhere (teammate, CI, prod)
```

`requirements.txt` yana buɗe muhalli **maimaita** — kowa zai iya sake ƙirƙira daidai alaƙa, yana hani "yana aiki a injina nawa" batutuwa.

## Kayan aiki na zamani

```text
venv + pip      → built-in, standard, widely used
poetry          → dependency management + lockfile + packaging (popular)
pipenv          → combines pip + venv with a lockfile
uv / pdm        → newer, faster tools
conda           → common in data science (manages Python versions + non-Python deps too)
```

Sabbin kayan aiki (poetry, uv) suna ƙara lockfiles da mafi kyau warware alaƙa, amma ainihin ra'ayi — muhallin da aka keɓe ga kowane aiki — shine gida.

## Koya komai ɓade daga ƙarewa halin kuri'a

```text
# .gitignore
.venv/        ← don't commit the environment; commit requirements.txt/lockfile instead
```

## Me ya sa haka mahalci

Sabannin muhallin Python shine mahimmi, shawara daidai don auki duk Python aiki — su hani rikicin alaƙa tsakanin ayyuka da kuma tsakanin ayyuka da system Python, da (tare da `requirements.txt`/lockfiles) buɗe muhallin sama da injin, abokan aiki, CI, da samarwa.

Bacin su yana haifar da rashin daidaita sifofi, karyan kayan aiki na tsarin, da muhallin da ba za'a iya maimaita ba.

Sanin yadda ake ƙirƙira, kunna, da ƙayyade dogaje — da muhallin kayan aiki na zamani (poetry, uv) — shine ainihin ilmi ga aiki na Python na gida da ainihin karatu a auki duk aiki na gida.