The dev host has only Python 3.14; the 0.13.205 pin needs 3.12 (its numpy has no 3.14 wheel). The pycares 4.5.0 workaround is no longer needed: verify_cleanup passes with pycares 5.2.1. Core 2026.x no longer treats a parked reauth flow as in progress for a new user flow with the same unique ID, so that path now aborts already_configured instead of already_in_progress. Both are translated; the test accepts either. Co-authored-by: Cursor <cursoragent@cursor.com>
14 lines
683 B
Plaintext
14 lines
683 B
Plaintext
# Test-only dependencies. The integration itself stays dependency-free
|
|
# (manifest.json keeps "requirements": []); this harness exists because
|
|
# config-flow behaviour cannot be exercised without a real Home Assistant.
|
|
#
|
|
# pytest-homeassistant-custom-component releases track core one-to-one.
|
|
# 0.13.375 pins core 2026.10.4 and requires Python 3.14, the interpreter on
|
|
# the dev host. Older pins (0.13.205 / core 2025.1.4) need Python 3.12:
|
|
# their numpy has no 3.14 wheel and will not build without a C compiler.
|
|
#
|
|
# python3 -m venv .venv-test
|
|
# .venv-test/bin/pip install -r requirements-test.txt
|
|
# .venv-test/bin/pytest tests/
|
|
pytest-homeassistant-custom-component==0.13.375
|