Python 3.10 reaches end of life soon, in 2026-10, and that will be a timely opportunity for LLMeter to drop support for it.
The main opportunity we expect from what's new in Python 3.11 would be to finally use Self as a type, closing some ugly typing workarounds - as mentioned by @acere in #54.
Conversely we should probably try to get away from from __future__ import annotations.
Dropping support for a Python version should probably constitute a major version update (at least to 0.2), so a good opportunity for us to review removing any other legacy compatability stubs floating around too. We should really try to prioritize proper multi-Python-version CI testing also - as proposed in #95
Python 3.10 reaches end of life soon, in 2026-10, and that will be a timely opportunity for LLMeter to drop support for it.
The main opportunity we expect from what's new in Python 3.11 would be to finally use
Selfas a type, closing some ugly typing workarounds - as mentioned by @acere in #54.Conversely we should probably try to get away from
from __future__ import annotations.Dropping support for a Python version should probably constitute a major version update (at least to
0.2), so a good opportunity for us to review removing any other legacy compatability stubs floating around too. We should really try to prioritize proper multi-Python-version CI testing also - as proposed in #95