`from future import annotations` is unnecessary on Python 3.14 #1

New issue

Open

opened 2026-08-16 23:02:35 -07:00 by justine · 0 comments

justine commented

2026-08-16 23:02:35 -07:00

Owner

The import was added to all eleven source and test files by habit rather than need. The ruff FA rule (flake8-future-annotations) came across with archivist's rule set and was satisfied instead of questioned.

This project has been requires-python = ">=3.14" since it was created. PEP 649 makes annotations lazy by default there, so PEP 604 unions, PEP 585 generics, and TYPE_CHECKING-only imports all work without the import.

Audit which files genuinely need it, remove it from the rest, and deselect FA so it does not demand the import everywhere again.

The import was added to all eleven source and test files by habit rather than need. The ruff `FA` rule (flake8-future-annotations) came across with archivist's rule set and was satisfied instead of questioned. This project has been `requires-python = ">=3.14"` since it was created. PEP 649 makes annotations lazy by default there, so PEP 604 unions, PEP 585 generics, and `TYPE_CHECKING`-only imports all work without the import. Audit which files genuinely need it, remove it from the rest, and deselect `FA` so it does not demand the import everywhere again.

justine referenced this issue from a pull request that will close it,

2026-08-16 23:02:46 -07:00

Remove unnecessary future annotation imports #2

justine referenced this issue from a commit

2026-08-16 23:12:27 -07:00

Cite the upstream bug behind the retained future imports

justine referenced this issue from a commit

2026-08-16 23:43:55 -07:00

Remove the last four future imports by importing at runtime