What Does a Python Developer Do on a Normal Work Day?

# Get the latest code from the main branch
git checkout main
git pull origin main

# Create a branch named after the ticket
git checkout -b feature/PROJ-214-export-orders-csv

# Activate the project's virtual environment
source .venv/bin/activate        # Windows: .venv\Scripts\activate

# Install any new dependencies teammates added
pip install -r requirements.txt

# Start supporting services (database, cache) in Docker
docker compose up -d db redis

# Apply new database migrations (Django example)
python manage.py migrate

# Run the development server
python manage.py runserver

# FastAPI projects instead use:
# uvicorn app.main:app --reload

# Quick sanity check that tests still pass on main
pytest -q

import csv
import io
from datetime import date

from fastapi import APIRouter, Query
from fastapi.responses import StreamingResponse

from app.db import get_orders_between  # existing helper

router = APIRouter()
COLUMNS = ["order_id", "customer_email", "amount", "created_at"]

def orders_to_csv(orders: list[dict]) -> str:
    buf = io.StringIO()
    writer = csv.DictWriter(buf, fieldnames=COLUMNS, extrasaction="ignore")
    writer.writeheader()
    writer.writerows(orders)
    return buf.getvalue()

@router.get("/admin/orders/export")
def export_orders(start: date = Query(...), end: date = Query(...)):
    orders = get_orders_between(start, end)
    body = orders_to_csv(orders)
    filename = f"orders_{start}_{end}.csv"
    return StreamingResponse(
        iter([body]), media_type="text/csv",
        headers={"Content-Disposition": f"attachment; filename={filename}"})

from app.orders_export import orders_to_csv, COLUMNS

def test_header_only_when_no_orders():
    out = orders_to_csv([])
    assert out.strip() == ",".join(COLUMNS)

def test_rows_written_in_column_order():
    orders = [{"order_id": "A1", "customer_email": "a@b.in",
               "amount": 499, "created_at": "2026-02-01",
               "internal_note": "ignored"}]
    lines = orders_to_csv(orders).strip().splitlines()
    assert lines[1] == "A1,a@b.in,499,2026-02-01"

# Run only these tests while working:
#   pytest tests/test_orders_export.py -q
# Run everything before pushing:
#   pytest -q

import logging

logger = logging.getLogger(__name__)

def get_orders_between(start, end):
    if start > end:
        # Bug found: users swapped dates and got an empty file
        raise ValueError("start date must be on or before end date")
    logger.info("export requested start=%s end=%s", start, end)
    rows = fetch_from_db(start, end)
    logger.info("export rows=%d", len(rows))
    return rows

# To pause and inspect variables while running tests:
#   breakpoint()   then: p start, p end, n (next), c (continue)
# Run one test with output visible:
#   pytest tests/test_orders_export.py -k swapped -s

# Format and lint (common tools: ruff, black)
ruff check . --fix
black .

# Run the full test suite
pytest -q

# Review your own diff before anyone else does
git status
git diff

# Commit with a clear message and push
git add -A
git commit -m "PROJ-214: add CSV export for orders by date range"
git push -u origin feature/PROJ-214-export-orders-csv

STANDUP (keep it under a minute)

Yesterday:
  - Finished PROJ-210 (order status filter), merged
  - Reviewed PR for payment retry logic

Today:
  - Start PROJ-214: CSV export for orders
  - Pair with QA on PROJ-208 retest

Blockers:
  - Need confirmation on time zone for export dates

## What
Adds GET /admin/orders/export?start=&end= returning a CSV.

## Why
PROJ-214 — admins need to download orders for reports.

## How
- orders_to_csv() builds the CSV (unit tested)
- start > end now raises a clear ValueError (test added)

## Testing
- pytest tests/test_orders_export.py (4 tests)
- Manually downloaded a 3-day export locally

## Notes for reviewer
- Large ranges may need pagination later; out of scope here

END-OF-DAY LOG (private notes)

Date: ________

Done:
  - PROJ-214 PR opened, CI green, 1 review comment fixed

Learned:
  - csv.DictWriter extrasaction='ignore' skips extra keys

Tomorrow first:
  - Address remaining review comment
  - Check export with QA on staging

Open questions:
  - Should export include cancelled orders?