Clean up .pytest_cache warnings in local/CI environment #6

Closed
opened 2026-06-23 23:14:51 +00:00 by rbrooks · 1 comment
Owner

Target release: v1.0.1

Investigate .pytest_cache warnings so cache behavior is clean for CI and local developer experience.

Source: SECURITY_AUDIT_REMEDIATION_PLAN.md → "Remaining non-blocking follow-up".

**Target release:** v1.0.1 Investigate `.pytest_cache` warnings so cache behavior is clean for CI and local developer experience. Source: `SECURITY_AUDIT_REMEDIATION_PLAN.md` → "Remaining non-blocking follow-up".
Author
Owner

Investigated on the updated dev server (main @ e9a05e2, pytest 9 / Python 3.12): ran the full suite with caching enabled (pytest -q -W default) → 307 passed, 0 warnings, no .pytest_cache-related warnings. pytest also writes its own .pytest_cache/.gitignore containing *, so the cache is already self-ignored and never shows in git status.

So there is no warning to clear on the current stack. The only real gap was hygiene: the project .gitignore didn't list the cache dir. Added .pytest_cache/ explicitly in ad57e0b. Closing.

Investigated on the updated dev server (`main` @ `e9a05e2`, pytest 9 / Python 3.12): ran the full suite with caching enabled (`pytest -q -W default`) → **307 passed, 0 warnings**, no `.pytest_cache`-related warnings. pytest also writes its own `.pytest_cache/.gitignore` containing `*`, so the cache is already self-ignored and never shows in `git status`. So there is no warning to clear on the current stack. The only real gap was hygiene: the project `.gitignore` didn't list the cache dir. Added `.pytest_cache/` explicitly in `ad57e0b`. Closing.
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
rbrooks/WeatherBot#6
No description provided.