build(test-django-cache-module): Migrate to uv and pyproject.toml

[ericapisani]

Summary

• Replace pip/requirements.txt with uv/pyproject.toml for dependency management
• Update run-django.sh and run-locust.sh to use uv run instead of manual venv creation and pip install
• Remove legacy requirements.txt

Refs PY-2441

Test plan

• Verify pyproject.toml includes all dependencies from the original requirements.txt
• Verify shell scripts use uv run
• Verify requirements.txt is removed

🤖 Generated with Claude Code

[linear-code]

PY-2441

[sentry]

Bug: The script installs uv but doesn't update the current shell's PATH. The subsequent uv run command will fail with "command not found", causing the script to exit.
_{Severity: HIGH}

Suggested Fix

After the uv installation, update the current shell's PATH before calling uv. One way is to source the environment file modified by the installer, for example: source "$HOME/.cargo/env". Alternatively, you can explicitly add the binary's location to the PATH: export PATH="$HOME/.local/bin:$PATH".

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: test-django-cache-module/run-django.sh#L4-L6

Potential issue: After installing `uv` via `curl`, the installer modifies shell
configuration files but does not update the `PATH` for the current, non-interactive
shell session. Because the script has `set -euo pipefail` enabled, the subsequent call
to `uv run` fails with a "command not found" error, which immediately terminates the
script. This bug will manifest in any environment where `uv` is not already installed,
which is the exact condition the installation block is designed for. The same issue
exists in `run-locust.sh`.

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 64301c2. Configure here.}

[cursor]

Unsatisfiable version constraint for memcache package

High Severity

The memcache package on PyPI only goes up to version 0.14.0, so the constraint memcache>=1.4.1 can never be satisfied and dependency resolution will fail. The version 1.4.1 appears to have been accidentally taken from the pymemcache package (listed on the next line), which does have that version. The original requirements.txt listed memcache without any version pin.

 

^{Reviewed by Cursor Bugbot for commit 64301c2. Configure here.}