Add PEP 749 compatibility

[JasonGrace2282]

Removes the required from __future__ import annotations to be compatible with PEP 749, which deprecates from __future__ import annotations

[Viicos]

It's probably too early to do so. from __future__ import annotations converts every annotation to strings, so that you can:

• safely use undefined symbols in the type annotation (e.g. attr: MyType = ...; MyType = int).
• use new typing features in older Python versions (which we still support), e.g. builtins subscripting, pipe syntax unions, etc.

[JasonGrace2282]

It's probably too early to do so. from __future__ import annotations converts every annotation to strings, so that you can:

• safely use undefined symbols in the type annotation (e.g. attr: MyType = ...; MyType = int).
• use new typing features in older Python versions (which we still support), e.g. builtins subscripting, pipe syntax unions, etc.

Sure, I'm not opposed to keeping those in the library by any means. I just wanted to remove the absolute requirement that __future__.annotations must exist (after a discussion with Jelle about his opinion on requiring the import).

[Viicos]

I see, as you wish, PEP 749 does not deprecate the import:

from __future__ import annotations (PEP 563) will continue to exist with its current behavior at least until Python 3.13 reaches its end-of-life. Subsequently, it will be deprecated and eventually removed.

(emphasis mine).

What's the benefit of not enforcing the import here? Imo this will only make people forget about it and then realize tests fails on 3.8/3.9 because they used new typing constructs.

[JasonGrace2282]

Fair enough, perhaps it's worth waiting.