Modules and virtual environments

Django projects are Python packages. You import apps with dotted paths, configure INSTALLED_APPS, and isolate dependencies in a virtual environment.

Imports in Django

from django.shortcuts import render, get_object_or_404
from blog.models import Article

Avoid circular imports—keep models lean, import views only where needed, use lazy references ("app.Model" strings) for ForeignKey when necessary.

Virtual environment workflow

1. python -m venv .venv
2. Activate: source .venv/bin/activate (macOS/Linux)
3. pip install django
4. django-admin startproject mysite

Commit requirements.txt; never commit the .venv folder itself.

Important interview questions and answers

1. Q: What is INSTALLED_APPS?
   A: List of Django apps whose models, templates, and static files are loaded—includes django.contrib.admin, your apps, and third-party packages.
2. Q: requirements.txt vs Pipfile?
   A: Both pin dependencies; teams pick one standard—reproducible installs matter more than the tool.
3. Q: Circular import fix?
   A: Move shared code to a third module, use string model references, or import inside functions.

Self-check

1. Why activate a venv before pip install django?
2. What does from blog.models import Article require in settings?