Open jorenham opened 2 weeks ago
It starting to look like unpy
could be battle-ready as soon as next week, at least the backporting stubs from Python 3.13 to 3.10 stuff, that is.
But I'm not yet sure what the best project-level integration strategy should be, because current static typecheckers should be able to understand it.
Perhaps a "mirror project" with its own pyproject.toml
is the way out here, but hopefully there's also a more "subtle" alternative approach (e.g. by using a .unpyi
extension or something)
The juicy unpy-only features (like type mappings and re-usable methods) will have to wait a little bit longer.
unpy
can now backport all python 3.13 .pyi
features to 3.10:
https://github.com/jorenham/unpy/releases/tag/v0.3.0
But it currently can only handle single .pyi
-> .pyi
conversion.
So integrating it here will have to wait until unpy
has the proper tooling to do so.
https://github.com/jorenham/unpy