Re: py-future does not support Python 3.13

[Taylor R Campbell <riastradh%NetBSD.org@localhost>]

> Date: Tue, 13 May 2025 13:01:10 +0200
> From: Thomas Klausner <wiz%NetBSD.org@localhost>
> 
> There's a backwards compatibility Python module called py-future that
> is intended to make code work on both Python 2 and 3.
> 
> Since Python 2 is mostly dead, this module is also not really useful
> any longer - it only makes sense for programs that want to support
> Python 2 and 3 from the same codebase.

Python 3 is still, after all these years, a severe regression in
performance and API stability over Python 2, and I think it is a
mistake to have gone so far in dropping Python 2 support -- it has
rendered Python a much less useful platform for everyone.

> Up to about an hour ago, the pkgsrc version of py-future didn't even
> support Python 3.12; the updated version, the final 1.0.0 release,
> does not support Python 3.13 (it uses two modules, uu and lib2to3,
> which were deprecated in 3.9/3.11 and were removed in 3.13).

Does it use them in libraries that other packages depend on, or in
developer tools that maintainers of the other packages might use?

As I understand it, 2to3 is mainly for rewriting .py source files, so
it's unlikely to be used as a library dependency.

The uu module has one call site surely that can't be hard to fix.